When comparing Gitblit vs sourcehut, the Slant community recommends Gitblit for most people. In the question“What are the best self-hosted web-based Git repository managers?” Gitblit is ranked 10th while sourcehut is ranked 20th. The most important reason people chose Gitblit is:
Setting up is easy and usage is intuitive.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Just works
Setting up is easy and usage is intuitive.
Pro Free and open source
GitBlit is free and open source (under Apache License) .
Pro Cross-platform
Gitblit is available for Windows, OS X and Linux.
Pro Built-in authorization in windows
So you don't have to worry about setting up OpenSSH on Windows.
Pro Lightweight
No javascript, drasticly light interface
Pro Email-Based Communication and Coordination
Unlike other services that make their communication services like mainstream social media, Sourcehut uses good old mailing lists to make things simpler. It capitalizes on git's "git send-email" feature. This is in adherence to Sourcehut's general design, which is to make simple, reliable products. The official website is at https://lists.sr.ht, and they have a tutorial on setting your git client up at https://git-send-email.io
Pro Includes build service
Sourcehut has an automated build service at https://builds.sr.ht that can build your code from it's repository. Because the project is in alpha, this service is currently free (they will build your projects for you for free!)
Pro "Pro" features are free since the project is still in Alpha
Because the project is in alpha, the "pro" features are free.
Cons
Con No code reviews
It's not possible to start any code reviews on Pull Requests
Con Access controls are repository-based
Built in access controls are not branch-based.
Con No Squash Merge
There is no Squash Merge functionality
Con No project admins
There's no separation between a system admin and a project admin. There's owners for projects, but to create a new repository one has to be a general admin.