Gogs vs SourceTree: What are the differences?
Gogs: A self-hosted Git service written in Go. The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows; SourceTree: A free Git GUI client for Windows and macOS. Use the full capability of Git and Mercurial in the SourceTree desktop app. Manage all your repositories, hosted or local, through SourceTree's simple interface.
Gogs can be classified as a tool in the "Code Collaboration & Version Control" category, while SourceTree is grouped under "Source Code Management Desktop Apps".
Some of the features offered by Gogs are:
- Activity timeline
- SSH/HTTP(S) protocol support
- SMTP/LDAP/reverse proxy authentication support
On the other hand, SourceTree provides the following key features:
- Full-powered DVCS
- Create, clone, commit, push, pull, merge, and more are all just a click away.
- Review your outgoing and incoming changesets, cherry-pick between branches, patch handling, rebase, stash, shelve, and much more.
"Self-hosted github like service" is the primary reason why developers consider Gogs over the competitors, whereas "Visual history and branch view" was stated as the key factor in picking SourceTree.
Gogs is an open source tool with 30.8K GitHub stars and 3.56K GitHub forks. Here's a link to Gogs's open source repository on GitHub.
9GAG, Typeform, and Zillow are some of the popular companies that use SourceTree, whereas Gogs is used by Write.as, OSInet, and GameDuell. SourceTree has a broader approval, being mentioned in 618 company stacks & 414 developers stacks; compared to Gogs, which is listed in 9 company stacks and 10 developer stacks.
What is Gogs?
What is SourceTree?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Gogs?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
GitKraken is the best git client so far. The user interface is very friendly. Everything is easy to do with this tool. A branch tree vizualization is very clear. I've tried SourceTree and I got lost in such many panels. Also performance of SourceTree is not as goot as GitKraken. I like Sublime Merge but it doesn't have so many features as the other tools. I've choosen GitKraken and as bonus I got GitKraken Glo that is the next perfect tool.
I installed Gogs after a few repos I planned to use on GitHub disappeared without explanation, and after Microsoft's acquisition of same, it made me think about the over-centralization of community-developed software. A self-hosted solution that enables easy point-and-click mirroring of important repositories for my projects, both in-house and 3rd-party, ensures I won't be bitten by upstream catastrophes. (So far, Microsoft's stewardship has been fine, but always be prepared). It's also a very nice way to host one's own private repos before they're ready for prime-time on github.
Gogs is written in Go and is easy to install and configure, much more so than GitLab. The only major feature I wish it had is an integrated code review tool.
Tower appears to be between GitKraken and SourceTree in detail, but gave two scary error dialogs when attempting to merge resulted in a conflict. Doing the same in SourceTree just worked and showed the conflict in its handy file view that's always visible (unlike Tower's mere "Merge branch 'X' into develop" message when the commit is selected).
Both GitKraken and Tower lack the commit hash in their history overview, requiring one to select a commit to see it.
GitKraken appears to be the only Windows 10 Git GUI suitable for night shifts, but like Tower is only free for 30 days, unlike SourceTree.
Used by various PrometheanTV technical staff to interface and interact with the Git Source Control service.
Since being familiar to git CLI, I nearly never open it again except using it as a diff tool.
Used Source Tree to maintain version / commit / pull request , merge of codes for a team.