A few years back I wrote an article on How to deploy a React application to Google Cloud using Bitbucket Pipelines. Since then I’ve moved onto another organization which uses my personal favorite, GitHub.
I’ve spent the last few weeks learning how to use GitHub Actions to automate my CI/CD process. In order to consider this a success I wanted to be able to run my tests, build, bump the version number, generate a change log and then deploy our package to NPM and our Storybook instance to GitHub Pages.
Below are the various configs that I setup for each of these steps. While there were a ton of resources out there about the individual steps, I couldn’t find any resources that put them all together.
Step 1: Lint, Test & Build
The first step is the most obvious step. Test it out and make sure it works before wasting a bunch of time crossing my fingers that all the yellow dots turn into green checkmarks.
In addition to my primary “release the kraken” workflow, I also have a PR verification workflow that does a lot of the same things. I wanted to have a simple config file that I didn’t have to copy/paste into multiple…
