Share your experience using Canonical Bazaar

GitHub serves as our primary platform for source code management, version control, team collaboration, code reviews, CI/CD automation, and issue tracking in software development. We store and manage source code in centralized repositories, hosting web application code in private repositories. We track code changes and maintain history using Git, with the ability to revert to a previous code version if an issue occurs. Code review is crucial to our process, as senior developers review and approve code before merging it into the main branch and running automatic tests after every code commit.

Our team collaborates on GitHub by using it for version control, CI/CD workflows, and collaboration. Developers collaborate on code changes through branches and pull requests. For issue tracking, we track bugs, enhancements, and development tasks by logging bug issues and assigning them to developers.

GitHub is deployed in our organization primarily to store application code, manage branches, review pull requests, and automate deployments. It supports code management, version control, collaboration, and DevOps automation across our software development team.

The best features GitHub offers include version control, repositories, pull requests, code reviews, issue tracking, and automation workflows. These features significantly improve collaboration, code quality, and development efficiency. Our development team uses pull requests and code reviews to validate and merge code changes before production deployment.

Automation workflows in GitHub help my team by providing capabilities through GitHub Actions, which automate software development workflows directly within repositories. Automation features such as CI/CD pipelines, automated build, test, and deployment processes run tests automatically after code commits or pull requests. Regarding deployment automation, we deploy applications automatically to environments, run recurring workflows on schedules, and automate alerts and approval steps. Whenever a developer pushes code, GitHub Actions automatically run unit tests and deploy the application after successful validation.

GitHub has positively impacted my organization by improving collaboration, code quality, version tracking, and development efficiency. It has helped multiple developers work on the same project without overriding code. The specific outcomes since using GitHub include faster code deployment cycles, improved code quality through reviews, better version control and change tracking, reduced code conflicts among developers, automatic testing and deployment workflows, and increased team collaboration and visibility. We see improvements in pull request merge time, deployment frequency, build success rate, issue resolution time, and code review completion time.

GitHub could be improved in several ways. Permission management and access control can become complex in large organizations, and advanced reporting with more built-in analytics and reporting for repositories and team productivity would be beneficial. The cost of enterprise features along with advanced security and enterprise functions can be expensive. Managing repository permissions across multiple teams and projects requires additional governance.

Common challenges I face include repository management, access control, and workflow handling. A pull request may fail to merge because another developer changed the same code section, causing merge conflicts. Common challenges in GitHub include merge conflicts, branch management complexity, permission governance, and troubleshooting automation workflows.

Other improvements needed for GitHub include better reporting, workflow debugging, repository governance, search efficiency, and notification management, such as better filtering of pull requests, issues, and workflow alerts. Easier policy enforcement across multiple repositories is also essential.

I have been working in my current field for five years.

GitHub is generally very stable and reliable, making it more scalable for larger projects. Our team uses it daily for source control and CI/CD pipelines, which indicates that GitHub can support day-to-day development activities with consistent performance and availability.

My experience with customer support is good. Our development team can raise support tickets for repository access issues, billing concerns, and CI/CD workflow problems. Customer support provides proper documentation and knowledge regarding the problems we face, along with good response times.

GitHub delivers a strong ROI by improving developer productivity, accelerating software delivery, and reducing manual effort. It saves money and time while also reducing the number of employees needed due to faster development and better code quality through reviews and lower operational overhead from tool consolidation.

Before choosing GitHub, we evaluated other options such as Azure DevOps and AWS CodeCommit, but we found that GitHub is the best solution for our organization.

Some common challenges I face include repository management, access control, and workflow handling. A pull request may fail to merge because another developer changed the same code section, causing merge conflicts. Common challenges in GitHub include merge conflicts, branch management complexity, permission governance, and troubleshooting automation workflows.

My advice for others looking into using GitHub is that I would recommend it to organizations seeking source code management, team collaboration, and DevOps automation. Development teams can utilize GitHub to manage repositories, perform code reviews, track issues, and automate CI/CD workflows with GitHub Actions, making it a strong choice for organizations that want efficient software development workflows.

GitHub is a strong choice for every organization and is a very good platform for any coder or software developer. It is a fantastic platform for organizations from my perspective. I would rate this product a 9 out of 10.

My main use case for Bitbucket is to collaborate on code, manage versions, then automate the software development life cycle, and design for professional teams to manage all repositories as well as for code reviews. I use Bitbucket for code preparation as well as code review.

The best features Bitbucket offers include code review, robust pull requests where a team can review code and leave comments, easy features for merging code, and the latest AI-powered insights, which includes Atlassian Intelligence that helps suggest code changes wherever team members want to change and identifies issues in broken builds while recommending reviews.

I use Bitbucket for automated pull requests, so whenever I use AI agents, they can automatically analyze code changes and generate comprehensive PR descriptions. That saves time for developers and ensures consistency across teams. Bitbucket helps me write code through an AI editor that can help write, summarize, and transform comments on my code, adjusting the tone of my responses to ensure clear and professional communications. Also, automated workflows, which I call robo-dev, are dedicated AI agents that can take actions on my behalf, such as handling code planning, performing code generation, and automating repetitive tasks at scale. Moreover, Bitbucket AI tools can act as an expert twenty-four seven, automatically scanning proposed code changes, highlighting potential bugs, spotting anti-patterns, and suggesting improvements before a human reviewer steps in.

Bitbucket has positively impacted my organization by saving time, managing code at one point, and helping track tickets assigned to team members via Jira. Everything can be managed from one point, making it very useful from both the Scrum and developer perspectives.

Bitbucket needs improvement as it has very limited cloud hosting options. With Atlassian phasing out its self-hosted server version, organizations are forced to choose between Bitbucket Cloud, which may not meet strict local compliance requirements, or a highly expensive data option. Additionally, Bitbucket is not competitive on pricing for scaling teams, as the free tier is great for up to five team members, but the jump in price for growing teams beyond five users can become steep compared to other repositories. Some enterprise users report that Bitbucket's stability can affect its speed when handling very large repositories, and though it has good support, the technical support team should be more active, as I have not seen them as active compared to GitLab and GitHub.

The limited cloud hosting options and pricing for scaling teams are two important areas for improvement.

I have been using Bitbucket for three years.

Bitbucket is very stable. Bitbucket provides the largest number of repositories with larger code, and I have not faced any issues related to stability. It is very good.

Some enterprise users report that while Bitbucket's stability and speed can degrade, it handles very large repositories at a very scalable moment.

I can rate customer support a nine out of ten as they are mostly available and provide quick solutions.

I had used GitLab before Bitbucket.

I switched from GitLab to Bitbucket because it depends on what tool the organization prefers. As a developer, I need to use what the organization is offering. Personally, I think people should go with GitHub if they are a solo developer or student or want to host public projects where others can easily find and contribute. Bitbucket is preferable if the company already uses Jira or Confluence or needs a cost-effective way to manage private repositories for small teams.

I do not have any relevant metrics at this time, but I see it can be useful for up to five team members. If more are needed, the organization must purchase extra at an additional cost. However, the deep integration with Jira means the organization does not need to pay extra because they can easily integrate with Bitbucket if they already have Jira. I can say the return on investment is very good compared to GitLab, but not better than GitHub.

Before choosing Bitbucket, I evaluated other options, including GitHub.

Bitbucket is deployed in my organization based on the client's requirement, integrated both on-premise and on cloud. I use AWS as my cloud provider. I purchased Bitbucket through the AWS Marketplace. I would recommend Bitbucket only if clients are using Jira or Confluence, and if they need a cost-effective way to manage private repositories for small teams, as it is a better option compared to GitHub and GitLab. I would rate this solution a seven out of ten.