Share your experience using Canonical Bazaar

I use GitHub for maintaining repositories, as it is easy to maintain freelance projects and to store college projects. I will be using it for hosting by providing a GitHub link.

For one of my freelance projects, I push the code or codebase to GitHub. From that repository, I get a link that I will host in Vercel or a Netlify platform. Then I will be able to get a public URL. That is how it is useful for me for freelance projects and college projects.

The feature I use the most is the GitHub clone feature because there are many repositories for study purposes, such as a portfolio or a Python-related project. I can easily clone the projects, open them in my window, and be able to work on them. That is the best feature I would recommend.

GitHub offers more options, such as more pro versions and more offers for GitHub Education, which I recently availed. The thing I wanted to add is the ease of maintaining repositories, and that is how it helps. It is a time-saving method because instead of having a manual method of hosting, I just push to GitHub, have the repositories, and then I am able to commit the changes easily.

The best features I will recommend are Copilot, then maintaining repositories is easier, then committing new updates, and the main feature is clone. I can easily clone GitHub repositories and open them on any other devices.

The feature I use the most is the GitHub clone feature because there are many repositories for study purposes, such as a portfolio or a Python-related project. I can easily clone the projects, open them in my window, and be able to work on them. That is the best feature I would recommend.

GitHub has many features, and it can be very good, such as having repositories. Also, some people are using it for the purpose of clearing doubts. There is something called asking doubts with someone else. Common people will be answering, and then I will be able to get badges to showcase on my profile. That is absolutely correct. Even the outcome metrics, such as if someone needs to hire me, they could be able to see my GitHub profile for the committed push and pull methods and all that, so GitHub will showcase my metrics.

Absolutely, it is money saved because instead of buying another cloud platform such as Google Cloud, I can easily maintain a repository and host it. Then it is also fewer employees needed because I do not need a big tech core for managing a database and repositories.

The thing that has frustrated me is sometimes when I push using a Git command, I need to force the push, which is the main thing. The setup is frustrating because GitHub could add a repository with pre-installed packages or something since I need to install packages in VS Code before pushing and maintain it in the codebase. Git packages need to be installed manually, and if that was already in a GitHub repository, that would be much better.

GitHub packages can be installed previously for the project upon the project requirement, and that is the thing I wanted to add here. That would be good.

According to governance and security, I recently heard about some security issues in GitHub. I think that could be centralized and should consider those security issues and clear them. The AI capabilities there include Copilot or something else.

I recently heard about security issues, but I do not know about it clearly. However, if security has been more tightened, it will be better.

I have been using GitHub for the past two to three years.

I have not experienced any downtime or issues. I received news about security issues, but other than that, I did not have any issues with it.

GitHub can handle my projects very well as they grow. I can easily give updates from VS Code and commit messages directly to the GitHub repository by just using Git commands.

I have not contacted customer support because I did not have any issues that required contacting them. I do not think customer support is something I have used, but I think they will be more good, especially when getting new features or offers.

Before using GitHub, I used a Netlify platform for small projects just with a drag and drop option. Later, I learned about GitHub, and then I switched to GitHub for maintaining repositories. Now, GitHub is one of my day-to-day activities.

When I first started GitHub, I thought it was too hard to do, hard to maintain, and the repositories were not being created with a proper method. Then later, I could understand and see many YouTube tutorials to understand GitHub and learn Git commands, which allowed me to easily adapt to GitHub. When I was starting first, I was really frustrated about what this tool was. At first, it was really difficult to understand, but later, after using it for three to five projects, I learned about GitHub. Upon the fifth project, it became very easy for me to maintain a GitHub repository.

I just keep it simple with Git. I have heard about GitLab, but I have not used it. I use GitHub with straight branching strategies, just a straight branch commit.

I have been using GitHub for free, and recently I got a free education offer, such as educational resources. I believe it is GitHub Pro or something similar. I have been using the educational offer, which gave me many resources for free, and I have used GitHub Copilot Pro for free as well. I have not encountered any initial setup cost for that.

I did not evaluate any other options. I just used a manual method in GitHub.

I use a private cloud here and also a public cloud; I use both private and public.

GitHub has many features, and it can be very good, such as having repositories. Also, some people are using it for the purpose of clearing doubts. There is something called asking doubts with someone else. Common people will be answering, and then I will be able to get badges to showcase on my profile. That is absolutely correct. Even the outcome metrics, such as if someone needs to hire me, they could be able to see my GitHub profile for the committed push and pull methods and all that, so GitHub will showcase my metrics.

If a new user is using GitHub, they should first learn about Git commands and directly push the repository, avoiding the drag and drop method. They should understand Git commands and from VS Code or their preferred IDE, they can push and maintain a repository. After pushing to the repository, they should be aware of the use cases of a repository. It is not just to maintain as a cloud; they can use it for hosting and other database connections.

Additional thoughts about GitHub include the potential to provide more resources for GitHub Enterprise. I have not used it, but I believe GitHub Enterprise should be beginner-friendly. My overall rating for this product is 9.5 out of 10.

My main use case for Liquibase is database change management inside our CI/CD pipelines. Before Liquibase, someone would have to manually run SQL scripts against the database and hope for the best.

Liquibase has positively impacted my organization by significantly increasing deployment frequency for database changes. We went from releasing database changes maybe twice a month because they were so manual and nerve-wracking to releasing them as part of every sprint.

I find it hard to put an exact number on how much deployment frequency increased, but the productivity gains are real. The manual database deployment process before involved a DBA, a developer, a change ticket, a scheduled maintenance window, and probably three to four hours of human time.

The best features Liquibase offers include the DATABASECHANGELOG table, which is deceptively simple but is the foundation of everything. Every change that has ever been applied is logged there, including who wrote it, when it ran, which environment, and the checksum.

Having that detailed tracking from Liquibase definitely helps me and my team day-to-day, making troubleshooting or audits easier.

Drift Detection is the other feature I would fight for, as the moment someone makes a manual change to a database outside the pipeline, it shows up. In a regulated environment, that is not just useful, it is necessary.

Liquibase can be improved by helping developers who have never used it before to understand change logs, change sets, contexts, and labels, which takes time. The documentation is good, but there is a gap between reading the docs and actually being confident with it.

I would appreciate more sophisticated pipeline analytics out of the box without having to set everything up manually.

I have been using Liquibase for a total of four years.

On a scale of one to ten, I rate Liquibase overall as an eight.

I rate it an eight because it fundamentally solved the problem that was genuinely painful and had not been solved well by anything else we evaluated.

Regarding Liquibase's AI capabilities, I think its governance and security are solid.

Regarding Liquibase's AI capabilities, I believe its accuracy and reliability of output could be improved.

We deploy Liquibase using GitHub Actions and Jenkins depending on the client environment. Liquibase itself runs as part of the pipeline job, connects to the target database, applies the pending change sets, and exits. There is no separate server to manage.

My experience with pricing, setup cost, and licensing is that the open-source version is free and genuinely capable for most use cases. We moved to Liquibase Secure for the governance features: audit logs, Drift Detection, policy enforcement, and separation of duties.