In my opinion, the best part of gearset is the ability to precisely deploy your changes. Meaning I can select specific changes that I made within each component and I can exclude any changes that are part of someone else's changes in the same component. This has made it so that if one person's changes are deploying before another's changes, they can without having to spend a great deal of time or rework getting one version ready for deployment. We previously used a tool that when you committed a component it committed everything including all changes. So if one set of changes had to deploy first, we had to go in and remove or comment out the other persons changes, Commit it again and then we could deploy it. Then we had to go in and replace or uncomment the changes we removed.

Rollbacks, easy to resolve conflicts when working on overlapping components, precise deployments of only necessary metatada (like not having to push an entire page), easy management of a proper dev pipeline that encourages best CI/CD practices

The user experience has clearly been thought through in detail. The CI/CD pipeline is straightforward to use and quick to learn, even as new developers come on board, and the integration with GitHub feels seamless.