There are lots and lots of events that can be used to trigger GitHub Actions. But if you want to control your actions programmatically from the outside you will need to use repository dispatch. In this post I will go through the essential things you need to know to trigger actions programmatically.
Would you like to be able to schedule the blog posts for your static site into the future but don't want to use up all of your free Netlify build quota? In this post we'll create a GitHub Actions workflow that triggers a site rebuild when a post has been scheduled to be published.
GitHub Actions gives you lots of freedom to define custom workflows by combining different actions and running command line programs. Sometimes you might want to run small snippets of code, and that is already possible by running scripts from the command line with the
run keyword. What if you could write your Python script inside the workflow YAML file instead?
There are plenty of actions available in the GitHub Actions Marketplace but sometimes you may come up with a use case that can't be solved with existing actions. In that case it is super useful to be able to create your own actions. That is what you will learn from this post.
Want to start using GitHub Actions but don't quite know how to get started? In this post I will explain Actions in an easily digestible way so that you can start adding useful logic to your repositories. This post will be full of examples so let's get going!