Share your experience using Canonical Bazaar

My main use case for GitHub is as a source code repository, utilizing GitHub Actions for process automations, CI/CD pipelines, deployment, and integration with the cloud and cloud machines.

A quick and specific example of how I use GitHub Actions for automations in my routine is that we use GitHub Actions for every production deployment. We have an automation that opens a change request (Gmud), which is very important for change management for our ISO 27001 certification.

GitHub has had a very positive impact on my organization. It helped us improve our SLA, our source code governance, our security, and our proactiveness in understanding and discovering vulnerabilities in our code, and it gives us more security for our certification. The automations and possibilities in the CI/CD pipeline also help us a lot by reducing manual work and increasing machine automation.

GitHub contributed to improving SLA and source code governance by enabling us to implement automations with GitHub Actions that were previously very manual. Many times, we had to wait for some tasks to finish before others could continue. For example, with the competitor I used before, I had to wait for the automated test of a pull request to finish before I could run another. Now, with GitHub, the tests run simultaneously and automatically, without one needing to wait for the other, which allows us to have less manual work. We don’t need to wait for one to finish to be able to send another pull request. We can do both at the same time and already solve the issues, improving our time, reducing manual work, and achieving around a 90% SLA reduction.

The best features that GitHub offers, in my opinion, are GitHub Actions with all its integrations and its possibilities of using AI, its automation capabilities, and the very complete source code repository with easy governance and a low learning curve.

Regarding GitHub’s AI features, I think their governance and security are very good. Governance is very easy to manage, and security is as well. AI is widely used to ensure security in our source code, so it’s good.

Regarding GitHub’s AI features, I also think the accuracy and reliability of the results are very good. The code that is reviewed by AI through Dependabot or GitHub Copilot review, for example, is very good and accurate. These tools provide good responses and good reviews, proactively finding vulnerabilities in the code or code that possibly has bad practices.

GitHub could improve its visual aspect a bit, specifically its UX/UI. It can be a bit confusing because there is a lot of information, and the screen can look somewhat cluttered. Maybe it could be simplified a bit more, or simplified versions could be created for users who don’t need so much information.

I have been using GitHub for three years.

GitHub is stable.

GitHub’s scalability is very good. It’s scalable in every direction through its integrations and connections.

Customer support is very good and fast.

I would rate customer support on a scale from 1 to 10 as a seven.

I previously used Bitbucket. We switched because of its very large limitations in automations, premium features, and AI.

I have achieved a return on investment. We reduced the time we spent on manual tasks or literally waiting for automations and processes running on the platform to finish, and we improved our SLA as a result.

We also had a positive ROI because the investment was small, only 10% above the cost of the previous solution we used, and we obtained many good cost-benefit gains, which helped improve our SLA and reduce our time. For example, we could reduce our team size to have a smaller payroll while maintaining the same delivery and proactiveness.

My experience with pricing, setup costs, and licensing has been very good. We use GitHub in its own cloud, and it’s very easy to do everything.

Before choosing GitHub, I evaluated other options, specifically GitLab.

I would rate GitHub overall a nine.

I choose the number nine because it’s very good, but it still needs to be a bit simpler and easier to learn for regular users.

My advice to others who are considering using GitHub is to study GitHub Actions a lot, because it’s very powerful and can help with many things. It seems simple, but in fact it’s very complex, and this complexity is a positive point because it can give you many benefits.

I use GitHub as my Git versioning platform, and my repos are also hosted on GitHub. I am using GitHub for versioning in my team.

I manage branches and pull requests using GitHub with strategies for deployments and merging, utilizing feature branches and permissions with approval gates for production deployments.

GitHub offers the best features including Git versioning, pipelines, Actions, version control, security, collaboration, PR management, and dependency management.

Collaboration, security, and version control, along with GitHub Actions, have had the biggest impact on my daily work.

I use some features less often, such as the secret and environment creations.

This workflow has improved my team's efficiency and collaboration by allowing us to plan deployments accordingly and easily roll back if something goes wrong.

GitHub has positively impacted my organization, helping to improve the productivity of my team and reducing errors in production.

If GitHub could support a GitOps approach for managing my Kubernetes clusters, that would be very helpful.

I have been using GitHub for almost seven years.

GitHub is stable.

GitHub's scalability is fine; I can customize it and have my own kernels.

The customer support does a great job, and I am happy they find solutions for my issues quickly. I would rate the customer support as a seven.

I started with GitHub, so I did not use any other options.

I was able to save time during deployments and optimize my spending, which helped me reduce costs.

I am happy with the pricing, and the setup cost is pretty much just a flat setup cost.

I checked other options before choosing GitHub.

I would rate GitHub as an eight overall.

Since GitHub has the features and functions I need in a DevOps bundle, I would say eight.

Regarding GitHub's AI capabilities, I find its documentation up to date, the governance transparent, and the security very much fine.

I am satisfied with GitHub's accuracy because whatever details I am getting are accurate and reliable outputs.

I am using GitHub in my private cloud, and sometimes I am using it in the public cloud as well.

My cloud provider for public or private deployments is Azure and AWS.

Since GitHub is a free solution, I advise others to start with their services, and for heavier workflows, you can run on your own runners as well.