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.
At a customer we're implementing GitHub Actions and even on our Dev environment there are so many hickups with GitHub.
Might be pricy though.
- SourceHut: https://sr.ht/~sircmpwn/sourcehut/
- Forgejo (used by Codeberg, etc.): https://forgejo.org/
Forgejo, on the other hand, is a drop-in replacement for GitHub.
- https://about.gitea.com/ (F/OSS MIT license self hosting GitHub like instance)