3 ms·

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 b

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.

motbus3 5mo ago
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?
- jeena 5mo ago
  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 5mo ago
    Demo of Gerrit here: https://gerrithub.io/q/status:open+-is:wip https://gerrithub.io/q/status:open+-is:wip
- Mashimo 5mo ago
  Jira / Bitbucket / Teamcity. Might be pricy though.
  - xp84 5mo ago
    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).
- strenholme 5mo ago
  Self-hosting with open source code: - SourceHut: https://sr.ht/~sircmpwn/sourcehut/ https://sr.ht/~sircmpwn/sourcehut/ - Forgejo (used by Codeberg, etc.): https://forgejo.org/ https://forgejo.org/
  - miroljub 5mo ago
    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.
  - strenholme 5mo ago
    Also: - https://about.gitea.com/ https://about.gitea.com/ (F/OSS MIT license self hosting GitHub like instance)
- olafmol 5mo ago
  Gitea might be an option also.
plqbfbv 5mo ago
> 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-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry 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.

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.

motbus3 5mo ago

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?

jeena 5mo ago
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 5mo ago
  Demo of Gerrit here: https://gerrithub.io/q/status:open+-is:wip https://gerrithub.io/q/status:open+-is:wip
Mashimo 5mo ago
Jira / Bitbucket / Teamcity. Might be pricy though.
- xp84 5mo ago
  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).
strenholme 5mo ago
Self-hosting with open source code: - SourceHut: https://sr.ht/~sircmpwn/sourcehut/ https://sr.ht/~sircmpwn/sourcehut/ - Forgejo (used by Codeberg, etc.): https://forgejo.org/ https://forgejo.org/
- miroljub 5mo ago
  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.
- strenholme 5mo ago
  Also: - https://about.gitea.com/ https://about.gitea.com/ (F/OSS MIT license self hosting GitHub like instance)
olafmol 5mo ago
Gitea might be an option also.

plqbfbv 5mo ago

> 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-packages-registry/working-with-the-container-registry#authenticating-to-the-container-registry 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.