GitHub Actions is now the most popular Build Platform on GitHub. But it is also much more than a CI system: it is a very powerful automation engine.
Let's take a look at how we can do CI with Actions, and how we can automate operations on our GitHub projects.
Today I want to talk about GitHub Actions, and explore with you what we can do with it. Many people in fact think that Actions are just meant for CI CD. But in reality the service does much more than that.
It is a pretty powerful automation platform that is able to respond to more than 90 events, including of course the code push to the repo, which will indeed start a CI run, but also many others that are not related to code.
For example, you can do something whenever a user creates a new Issue, or when they open a Pull Request. Or even when a new comment is added.
Basically, if you can automate it you can do it with Actions!
To show you what you can do with Actions, I created some examples (which I have also used during the Hong Kong Opensource conference I've presented at last week) and I've gone through them in the video below.
Enjoy the watch!
This was a quick showcase of what you can do with GitHub Actions.
But as I've said before, you are by no means limited to what I've shown you here. You can do much much more.
You can take a look at the example in the Github Repo I've created, and please leave me a comment below to let me know:
- Do you already use Actions for something non CICD-related?
- What do you think of GitHub Actions?
- Do you have any other question?
Like, share and follow me 🚀 for more content: