Lately I’ve started moving code projects away from CircleCI and just to use Github Actions natively within our repos. There’s absolutely nothing wrong with CircleCI! But, it’s still one more service to configure and pay for when we’re already paying for Github Actions along with our organizational account. So in an effort to tidy up a bit, we’ve switched over our CI pipelines to use Actions instead.

One of the issues I found while transitioning to Github Actions was with our Heroku Pipeline. With CircleCI, Heroku automatically had build status information on each commit. This way we could see exactly which builds passed or failed before we promoted the app to production.

I searched for solutions to this and couldn’t find anything that did what we needed, so I created my own little process.

If you’re using Heroku Pipelines and Github Actions, here’s how to get those little green checks back during your build phases.