Bitbucket is a Git repository and code collaboration platform, featuring automated testing and code deployment. Bitbucket Cloud Premium provides AI-powered development, more granular access controls, and enforced code quality, and Bitbucket Data Center provides a self-hosted option.
$0
for up to 5 users
GitHub
Score 9.0 out of 10
N/A
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans are available.
The majority of SCM tools are Git based. What makes this solution stand out from the rest is it's web-based interface, which implements version control standards very intuitively. As a result, the learning curve shortens and productivity is highly improved.
Data Analyst, Regulatory Affairs and Quality Assurance
Chose Bitbucket
I didn't choose Bitbucket, but I hypothesize that my company chose it partly for its phenomenal integration with other Atlassian products such as Jira. Bitbucket has GitHub as a worthy competitor, but in my opinion, there are no real Jira Software competitors.
I have used Gitlab and Github in the past. While Gitlab is good if you are finding an open source solution for your code management and Github is good for the open source contribution, Bitbucket is an ideal choice to build an enterprise level product. The ecosystem that Jira …
I have used GitHub and GitLab before working on Bitbucket. There is no huge reason to choose Bitbucket over others. The only thing I like more about Bitbucket is security and user interface!
When we make the choice of using BitBucket at that time we didn't have a choice. It was better than GitHub but nowadays GitHub is not just a source control tool it's a DevOps platform. If we talk about GitLab it is even better than GitHub. We're in the process to phase out …
The main reason why we choose Bitbucket is because they provide a secure way to save the code using private repositories. The Access control is easy to setup too
Bitbucket is perfect for our business because it allows us to work on private projects and integrate seamlessly with our existing tools. They also provide a nice app called Sourcetree to help developers work on git environments without experience with git command-line …
When GitHub was acquired by Microsoft my previous organization had concerns about paywalls and additional restrictions that might be placed on the projects. We had made a move to Bitbucket as a result. The acquisition didn't seem to have any implications on the overall …
For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more …
1. Github is open source and also many security vulnerabilities because it is open source. That's one of the main reasons we chose BitBucket. 2. BitBucket integrates natively with other Atlassian tools without any custom configurations.
I have used Tortoise SVN in the past with various teams. Tortoise SVN is open-source and has a lot of valuable functionality built in. That being said, Bitbucket is more user-friendly being that there is a decent user interface. The UI is not great, but it still makes working …
Bitbucket integrates with Confluence and Jira more easily than GitHub, which was a plus for us, given that we already used those tools extensively. Additionally, the pricing structure for Bitbucket makes it more affordable for our organization, which is especially important, …
Gitlab provides lesser features compared to Github. Gitlab/GitHub are both from a different company (Atlassian), which makes it tough to interrelate projects with other task management tools offered by Atlassian.
Github is a good repository to store and share code files. But Github is open to the community and public. But keeping the research codes private before publication is possible in Bitbucket.
Bitbucket is good for private repositories and reliable CI/CD integration but it's getting behind Github which every day has more and more integrations and which in my opinion has a larger customer group. Gitlab also offers some good support for private repositories but the …
We did select Bitbucket for a bit, but then we eventually moved away from using JIRA to different tools and as a result, it made more sense to move our source code to GitHub since it provides more features and is just much easier to use as everyone already knows how to use …
All 3 software works well for development and source code control, but for sure Bitbucket is the easiest to be set up and be deployed among the team. The integration with JIRA makes this a powerful tool against coding-only applications. However, for open source, it would be …
Of the three, we mostly use Gitlab the most. I don't know why as I was not part of the selection process. But if I'm to guess, this is an organization preference. Our company uses Bitbucket the most, while our partners either use Gitlab the most and sometimes ButBucket. But if …
At the time of making the selection, Bitbucket offered free private repositories when no one else did. This was the primary motivator. With GitHub, you can now have free private repositories on personal accounts, but organizations must still pay for private accounts. Overall …
Bitbucket was my repo host of choice when it came to private repos, but now that GitHub offers free private repos I’ll probably just use them. If you want to manage branch protection though you’ll need a Pro membership for GitHub whereas it was free with Bitbucket.
I think Gitlab and Bitbucket are very similar. I am very familiar with git commands so its easy for me to use both. But I would still prefer Gitlab since it has few additional features like send merge request, approvers etc.
From a cost standpoint, Bitbucket is the winner if you fall outside of the ability to use the Github and Gitlab free tiers. Both of those solutions have their own merits, but from a cost saving perspective Bitbucket is more than likely going to be the most effective option.
Bitbucket uses Git as a client which is more advanced with lots of features for source code management tool. It is very easy to scale horizontally as per our needs, and recent new features like adding multiple file systems keep Bitbucket more useful. Due to multiple file …
GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular …
Over my career I've used a variety of other platforms but always find myself coming back to GitHub which has always had the most forward thinking features, evolving faster than other platforms, staying on the cutting edge of AI and other tools as they are released. AI …
GitLab has strong code review and project management capabilities, but it has a smaller community. Better for cross-functional collaboration but less intuitive for nontechnical users.
GitHub compared to Gitlab and Bitbucket seems to have an easier and nice to use interface. This is mainly due to the fact that GitHub is the No1 choice for most of the Open Source projects. Developers out there are already famaliar to it's UX/UI and use it every day.
GitHub is primarily targeted at developers and open-source communities, while Bitbucket is geared more towards small- to medium-sized businesses. GitHub has a free plan for open-source projects, while Bitbucket charges a fee for private repositories. For organizations with …
GitHub is the best platform to manage your source code. You can manage your CI/CD with different cloud service provider platforms and different languages. You can also create GHE for a number of organizations and repositories. Learning GitHub is easy and simple and supports …
GitHub stacks up against all of its competitors due to its ease of use and great UI that tops the all. I selected GitHub considering its popularity greater developer community. GitHub also provides Student Developer Pack that we can use to enhance our knowledge and get up to …
While SVN comes with basic functionalities, TFS is a superior tool and often unused to its potential in most cases. GitHub brings that equilibrium. It perfectly works like a versioning tool and can also be used to create CICD deployment pipelines.
GitHub is distributed model while perforce is more centralised .i.e. Developers can easily download full change history. Git is better in terms of performance as it provides faster result. Also Git is open source and available free of cost. Git is also storage effective with …
One biggest reason is that GitHub is popular and used by many so it is easy to get contributions this also means that most people are already familiar with using GitHub. Gitlab does offer more features and has more rich pipelines with the free repository as well but GitHub is …
GitHub is awesome at it's own place. I'm using it from last 3 years and not used so Gitlab or Bitbucket so much. They are also having almost same features but i think one of then is free for multiple branches.
GitHub gives support for open-source applications. I think it has an easier and more reliable interface compared to other products on the market. You are able to expose your work via GitHub so that it can be used as a proof of your work to your current employer or future …
GitHub is the de-facto solution for version control and code storage. Our team prefers it over other options like BitBucket for its feature-completeness.
GitHub is at least as good as BitBucket, if not a little more refined. GitHub is hands-down better than TFS. If you are using TFS, you really need to move to a modern source control system. The newer Azure DevOps Server has a decent Git offering, but the UX is incredibly …
In the past, we used Beanstalk and were happy with it. Going forward, GitHub makes it easier for us to work with open-source projects and with new temporary developers who might not be familiar with Beanstalk.
GitLab is my personal preference for source control, primarily because of the fact that it is open-source, and that it has great CI tools integrated directly into the service. However, GitHub is probably the leader with respect to enterprise offerings. GitHub has many more …
As a team we need to push code into the repo on daily basis, Bitbucket has proven that is a reliable and secure server to save and get the code available in no time. The administration part is really easy and there's an extra tool for every developer profile either if you want to use the console or a GUI like Sourcetree.
I’ve worked with Github my entire career and view it as an essential part. As a Product manager it allows me to keep track of my features, epics, issues and QA. It is easy to set up and integrate with tools such as intercom or notion.
Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.
While it integrates flawlessly with other Atlassian products, it's lacking in 3rd party integrates, especially compared to competitors like GitHub and GitLab
Using Jira for issues gives a lot of power, but it's also a lot of overhead and complexity that may or may not be necessary for your organization. It also puts issues in another tool, adding a little friction when it comes to addressing issues in your code
Searching for and discovering other projects and GitHub isn't quite as intuitive or easy to use as competitors
Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.
All products have room for improvement. The system improves over time with better and better integrations and I look forward to even more features without paying extra! The system has increased transparency across my organization and with this transparency comes increased throughput on projects. I don't think I can go back to any other system and we are definitely married to this product.
GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.
The architecture of Bitbucket makes it more easily scalable than other source code management repositories. Also, administration and maintaining the instance is very easy. It integrates with JIRA and other CI/CD applications which makes it more useful to reduce the efforts. It supports multiple plugins and those bring a lot of extra functionality. It increases the overall efficiency and usefulness of Bitbucket.
GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.
The customer support provided by Atlassian (Bitbucket's parent company that also makes Jira, Confluence, etc.) is very helpful. They seem to be very concerned about any issues reported with their products and even just questions about functionality. They are constantly improving the products with new features in nearly every release. Plus they have a plethora of online documentation to reference.
It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.
For the features we were looking at, Bitbucket, GitHub and GitLab were all at par and were in a similar price range. We found that GitHub was the most full featured should we need to scale very quickly. GitLab was at par with GitHub for our future needs, but GitHub was a more familiar tool compared to GitLab. Bitbucket won out because of its close integration with Jira and being in the Atlassian family. It was also cheaper than GitHub. As we started with Jira, Bitbucket addition became a natural next step for us. We really liked Bitbucket and stayed with it but we do know we have great options in the form of GitHub and GitLab should we need to scale fast.
GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular tool many other platform provide easy integration with the platform and make first choice for many tools architects.
The overall return on investment is very high compared to other source code management tools.
Having a subscription model only is making BitBucket's cost of ownership very high over the years. There should be an alternative option for the purchase of a license permanently (like proprietary software).
Paying separately for premium support is not a good idea. Premium support should be part of the package itself.
No local or on-call support available in Singapore and many other countries is also painful. There should be some local presence, at least in their leading market countries like Singapore.
GitHub has made branching much easier for our dev team. Easy branching makes it easier for us to gain all the benefits of source control while giving us the flexibility to decide what features/branches we want to go in any particular release.
Integration with third-party tools like Azure DevOps has allowed us to streamline workflows and gain the benefits of automated testing whenever a commit is made.
GitHub has also raised visibility with its integration with our Sprint boards. We can easily jump to a commit from a work item.