🧪 Experimenting with git hooks to generate @ChangesetsJS files based on the commit message.
It takes the good parts of semantic/conventional commit messages (source of truth) to automate some pain points with authoring changesets.
Best of both worlds? Time will tell.
🫰✨ @Shopify devs can /snapit in a Polaris pull request to have it publish an NPM package snapshot of their branch.
No more yalc, -alpha.29 and added process that slows us down shipping fast at scale.
@ChangesetsJS @_samrose3_ @github 🚀
https://t.co/dyyaRMeTqN
@jmsfbs@AndaristRake We were actually storing all the data in git originally!
The two problems we found were:
Changesets couldn't be edited easily. Changesets use full markdown spec now, and can be very rich
In very active repos, that much info in git eventually slowed git down.
@threepointone Just to check as well, what’s the main feature you want from an app separate to simply failing CI if there’s no changeset present? Basically what we do on GitHub?
Note: this and being able to tag every package in your monorepo on npm were originally going to be @ChangesetsJS features, but didn't quite fit there.
If you're using changesets you should probably have a look at this.
🎉We've added some new features to the Changeset Bot:
✅ You can now see a list of packages that the changesets in a PR will release
✅ The link to add a changeset will now prefill the packages based on the packages that have changed.
🦋https://t.co/0SSEbDKZ1W
I built a thing! Very new, may break:
https://t.co/X73bv3NJdb
View the changelog for any npm package (if the changelog is published to npm)
TY @mitchellhamiltn for inspiration, @thethinkmill for supporting it 💖