I'm on the other side of the fence. We're just about done migrating from GitHub to GitLab (self-hosted) and it's been refreshing to DGAF about any of the GH outages I read about.

▲

embedding-shape 3 hours ago | parent | next [-]

Similar boat myself too, finished moving all important stuff from GitHub to self-hosted Forgejo with cross-platform builds. Not only do I avoid all the downtime stuff, but E2E builds also takes ~20% of the completion time it used to take, since now my runners have dedicated hardware hosted at home.

▲

rmaus 2 hours ago | parent [-]

To maintain a fair comparison, GitHub has supported self-hosted runners for several years (maybe that doesn’t work for your specific usage, for whatever reason).

	▲	embedding-shape 2 hours ago \| parent [-]
		> To maintain a fair comparison, GitHub has supported self-hosted runners for several years Yeah, tried that first, as I didn't want to move to Forgejo, I just wanted to keep working when I wanted to work. The GitHub runner on Linux seemed fine, but the ones for macOS and Windows seemingly did something that made them a hell lot slower than even running VMs and then executing stuff inside those. I'm not sure what the runner is doing, if there is some built-in sandboxing or what not for those platforms, but it wasn't feasible to rely on for me as the builds took way too long time.

▲

anilakar 3 hours ago | parent | prev [-]

We were on self-hosted Gitlab but after a merger were forced to Github. Navigation feels painful in comparison and basic features such as commit graph are now behind more expensive tiers.

▲

plqbfbv 15 minutes ago | parent | next [-]

> We were on self-hosted Gitlab but after a merger were forced to Github. Navigation feels painful in comparison and basic features such as commit graph are now behind more expensive tiers.

Same experience here. Add to that that even on Enterprise tier:

- 1 Enterprise : 1 namespace - although you can segment it with Orgs, we were advised not to do it because we're too small (~2k people) (GL: groups, subgroups, sub-subgroups, ...)

- SSH deploy keys are singletons across the entire instance and repo-bound (and Weblate for instance can only use its own key), so you need a service account for that (GL: instance-wide SSH deploy keys that you can activate in specific repos)

- GHCR only really supports classic PATs for authentication ( https://docs.github.com/en/packages/working-with-a-github-pa... - GL: proper deploy keys properly inherited throughout the hierarchy)

So all in all the experience so far is a huge step-down. I really liked pinning commonly accessed pages in the sidebar.

▲

motbus3 3 hours ago | parent | prev [-]

Interesting! I worked with Gitlab and I also thought it was quite clunky. If it was not for the stability issues GitHub is fine. Any other alternatives to GH or GL?

▲

strenholme 2 hours ago | parent | next [-]

Self-hosting with open source code:

- SourceHut: https://sr.ht/~sircmpwn/sourcehut/

- Forgejo (used by Codeberg, etc.): https://forgejo.org/

	▲	miroljub 2 hours ago \| parent [-]
		SourceHut never really clicked for me. It doesn't give me anything useful that I don't already have in a bare git repo through a ssh. Forgejo, on the other hand, is a drop-in replacement for GitHub.

▲

olafmol 38 minutes ago | parent | prev | next [-]

Gitea might be an option also.

▲

jeena 3 hours ago | parent | prev | next [-]

We switched from Bit bucket to Gerrit internally and it was a steep learning curve for the des but it's fine.

At a customer we're implementing GitHub Actions and even on our Dev environment there are so many hickups with GitHub.

	▲	Mashimo 3 hours ago \| parent [-]
		Demo of Gerrit here: https://gerrithub.io/q/status:open+-is:wip

▲

Mashimo 3 hours ago | parent | prev [-]

Jira / Bitbucket / Teamcity.

Might be pricy though.

	▲	xp84 2 hours ago \| parent [-]
		Having used Teamcity for CI I cannot think of a more clunky and hard to use system (compared to GHA, which is what we migrated to).