Bitbucket vs SourceTree: What are the differences?
What is Bitbucket? One place to plan projects, collaborate on code, test and deploy, all with free private repositories. Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
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.
Bitbucket and SourceTree are primarily classified as "Code Collaboration & Version Control" and "Source Code Management Desktop Apps" tools respectively.
Some of the features offered by Bitbucket are:
- Unlimited private repositories, charged per user
- Best-in-class Jira integration
- Built-in CI/CD
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.
"Free private repos", "Simple setup" and "Nice ui and tools" are the key factors why developers consider Bitbucket; whereas "Visual history and branch view", "Beautiful UI" and "Easy repository browsing" are the primary reasons why SourceTree is favored.
PayPal, Salesforce, and Starbucks are some of the popular companies that use Bitbucket, whereas SourceTree is used by Zillow, PedidosYa, and Coderus. Bitbucket has a broader approval, being mentioned in 1735 company stacks & 1449 developers stacks; compared to SourceTree, which is listed in 615 company stacks and 400 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?
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.
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.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Bitbucket?
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
Sign up to get full access to all the tool integrationsMake informed product decisions
I was looking for an alternative to GitHub, where I could store my own private repositories. BitBucket filled that need and has performed extremely well.
I use Bitbucket's git repositories as a low cost config sync between servers.
We use Bitbucket and Bitbucket Pipelines because of its tight integration with JIRA and code authorization features.
The primary drawback is that its extension ecosystem (e.g., PR review tools) is miles behind Github
Best GIT repository management software that allows free closed-source projects. Also works seamlessly with other Atlassian products.
Great private repository capabilities that can be used for continuous integration in conjunction with Jira and Bamboo.
had to use it as a couple of clients had repos on it. worst of the git services. i try to stay far far away.
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.