When comparing GitHub Enterprise vs sourcehut, the Slant community recommends GitHub Enterprise for most people. In the question“What are the best self-hosted web-based Git repository managers?” GitHub Enterprise is ranked 8th while sourcehut is ranked 20th. The most important reason people chose GitHub Enterprise is:
GitHub's UI is clean and intuitive. Each view is designed to not fill the screen with useless information. For example, the repository view displays only the most crucial data about that repo - on the top it displays the number of commits, branches, releases and contributors. When clicked, each of them will take the user to a page that displays more detailed information.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Nice and usable UI
GitHub's UI is clean and intuitive. Each view is designed to not fill the screen with useless information.
For example, the repository view displays only the most crucial data about that repo - on the top it displays the number of commits, branches, releases and contributors. When clicked, each of them will take the user to a page that displays more detailed information.
Pro Support for various cloud hosting platforms
GitHub enterprise is available for Amazon AWS, VMware and now on OpenStack KVM as well.
This facilitates the use of GitHub Enterprise for people already familiar with these platforms and allows teams to keep using their infrastructure of choice.
Pro JIRA integration
When linked to JIRA, branches, commit messages and pull requests can all reference JIRA issues. This allows JIRA to display information about your development activity in the corresponding issue.
Pro Powerful search functionality
GitHub Enterprise has powerful search features that allow users to search by file name or project name. It's one of GitHub's most powerful tools.
Pro LDAP support
GitHub has improved the LDAP performance. By optimizing searching strategies, they have reduced significant network IO and total queries. Therefore, in some cases as much as 40 percent less data is transmitted on sign on.
Pro Gists support
Gists are ways to share code or have conversations about anything without needing a full git repo, and still, they work as git repos so they are versioned, forkable and usable from git.
Pro GitHub Enterprise dows not render just markdown
GitHub does not render just markdown, it also renders geojson files, 3D models and csv files.
Pro GitHub has the ability to edit code right on the web page
With GitHub Enterprise edits to code files and to files in general can be made inline right on the web page UI.
Pro 45-day trial available
There is an option to test GitHub Enterprise for free for 45 days.
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 Proprietary
If being proprietary in general is not bad enough, it's owned by Microsoft.
Con Can't natively manage large files and binaries (yet)
Max file size limited to 100MB. Git Large File Storage (GLFS) is in the works, but not ready yet. No other native options for large file/binary management.
Con No Continuous Integration packaged into the software
You'll have to set up Jenkins or pay for CircleCI, Travis, etc. in order to get CI running alongside GitHub Enterprise.
Con Update cycle lags behind public github
This is intentional, could be seen as advantageous.