Need advice about which tool to choose?Ask the StackShare community!
GitHub vs SourceTree: What are the differences?
What is GitHub? Powerful collaboration, review, and code management for open source and private development projects. GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
What is 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.
GitHub 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 GitHub are:
- Command Instructions
- Source Browser
- Git Powered Wikis
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.
"Open source friendly", "Easy source control" and "Nice UI" are the key factors why developers consider GitHub; whereas "Visual history and branch view", "Beautiful UI" and "Easy repository browsing" are the primary reasons why SourceTree is favored.
Airbnb, Netflix, and Medium are some of the popular companies that use GitHub, whereas SourceTree is used by 9GAG, Typeform, and Zillow. GitHub has a broader approval, being mentioned in 4712 company stacks & 6092 developers stacks; compared to SourceTree, which is listed in 618 company stacks and 414 developer stacks.
Do you review your Pull/Merge Request before assigning Reviewers?
If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:
- Pick the correct target branch
- Make Drafts explicit
- Name things properly
- Ask help for tools
- Remove the noise
- Fetch necessary data
- Understand Mergeability
- Pass the message
- Add screenshots
- Be found in the future
- Comment inline in your changes
Read the blog post for more detailed explanation for each item :D
What else do you review before asking for code review?
Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.
SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.
As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?
One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but
git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.
It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.
Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.
Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!
I explored many Git Desktop tools for the Mac and my final decision was to use Fork. What I love about for that it contains three features, I like about a Git Client tool.
It allows * to handle day to day git operations (least important for me as I am cli junkie) * it helps to investigate the history * most important of all, it has a repo manager which many other tools are missing.
At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.
Pros of GitHub
- Open source friendly1.8K
- Easy source control1.5K
- Nice UI1.3K
- Great for team collaboration1.1K
- Easy setup864
- Issue tracker503
- Great community484
- Remote team collaboration480
- Great way to share450
- Pull request and features planning441
- Just works145
- Integrated in many tools131
- Free Public Repos119
- Github Gists114
- Github pages110
- Easy to find repos82
- Open source61
- Easy to find projects59
- It's free59
- Network effect56
- Extensive API48
- Developer Profiles33
- Git Powered Wikis32
- Great for collaboration29
- It's fun23
- Community SDK involvement22
- Clean interface and good integrations22
- Learn from others source code19
- Because: Git15
- It integrates directly with Azure14
- Standard in Open Source collab9
- It integrates directly with Hipchat8
- Beautiful user experience7
- Cloud SCM6
- Easy to discover new code libraries6
- Smooth integration5
- It's awesome5
- Nice API5
- Quick Onboarding4
- Remarkable uptime4
- Hands down best online Git service available4
- CI Integration4
- Loved by developers3
- Free HTML hosting3
- Security options3
- Simple but powerful3
- Uses GIT3
- Unlimited Public Repos at no cost3
- Version Control3
- Easy to use and collaborate with others3
- Nice to use2
- Easy and efficient maintainance of the projects1
- Good tools support1
- Free HTML hostings1
- Self Hosted1
- All in one development service1
- Easy to use1
- Easy source control and everything is backed up1
- Leads the copycats1
- Never dethroned1
- IAM integration1
- Issues tracker1
- Very Easy to Use1
- Easy deployment via SSH1
- Free private repos1
Pros of SourceTree
- Visual history and branch view205
- Beautiful UI164
- Easy repository browsing134
- Gitflow support87
- Interactive stage or discard by hunks or lines75
- Great branch visualization22
- Ui/ux and user-friendliness18
- Best Git Client UI/Features8
- Search commit messages7
- Available for Windows and macOS5
- Log only one file1
- Search file content1
Sign up to add or upvote prosMake informed product decisions
Cons of GitHub
- Owned by micrcosoft53
- Expensive for lone developers that want private repos37
- Relatively slow product/feature release cadence15
- API scoping could be better10
- Only 3 collaborators for private repos8
- Limited featureset for issue management3
- GitHub Packages does not support SNAPSHOT versions2
- Does not have a graph for showing history like git lens2
- Have to use a token for the package registry1
- No multilingual interface1
- Takes a long time to commit1
Cons of SourceTree
- Crashes often11
- So many bugs8
- Fetching is slow sometimes7
- Extremely slow5
- Very unstable5
- Can't select text in diff (windows)4
- No dark theme (Windows)4
- Can't scale window from top corners3
- Freezes quite frequently3
- UI blinking2
- Installs to AppData folder (windows)2
- Diff makes tab indentation look like spaces2
- Windows and Mac versions are very different2
- Windows version worse than mac version2
- Diff appears as if space indented even if its tabs2
- Doesn't have an option for git init2
- Useless for merge conflict resolution2
- Doesn't differentiate submodules from parent repos2
- Requires bitbucket account2
- Generally hard to like1
- No reflog support1
- Bases binary check on filesize1
- Can't add remotes by right clicking remotes (windows)1
Sign up to add or upvote consMake informed product decisions
What is GitHub?
What is SourceTree?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with GitHub?
Sign up to get full access to all the tool integrationsMake informed product decisions