GitHub Actions has gone through some exciting changes recently! Now in public beta, the new and improved Actions is empowering developers to automate their workflow in new and exciting ways, all on GitHub.
To figure out what all the buzz was about, I decided to build a simple automation workflow. I’ve used Jenkins before, but didn’t find it to be super intuitive, and the ability to define workflows with some simple YAML — and have the workflows run directly on GitHub — was attractive to me.
My first workfl ow was a somewhat simple test and release workflow. When I push my code up to GitHub, I want to be able to release it immediately, with no additional work required. Naturally, I also want some level of confidence that I won’t be releasing broken code, so I’ll make sure the code is tested first.
Before we dive into some examples, a quick caveat: this post is not intended to be a full tutorial on how to use Actions, and I won’t define all the steps in the process. If that’s what you’re looking for, I’d recommend checking out my colleague Jeff Rafter’s fantastic article. Also, the workflow outlined in this post is admittedly simplified, but there are some interesting concepts worth covering, so please enjoy!