In my last article, I did an overview of GitHub Actions and demonstrated how to use an existing action to deploy a Gatsby site to GitHub Pages. In this post, I’d like to dive deeper into GitHub Actions exploring the underlying motivation behind them, the architecture, and the steps involved in building a custom action.
Before getting into the specifics of GitHub Actions, let’s understand the value they bring by first delving into GitHub events and how GitHub has been supporting the handling of these events.
GitHub provides hosting for software projects and version control using Git. It has formed the nucleus of the software development lifecycle by supporting collaboration across teams (often distributed), code reviews, and project management. …
In my previous posts exploring GitHub Actions, I’ve delved into how to use public Actions on the GitHub Marketplace. In this post, I’d like to go over how to efficiently navigate the Marketplace as a developer.
There are two ways to search for public GitHub Actions.
The GitHub Marketplace is home to two kinds of tools that extend GitHub’s core functionality:
To search for Actions directly in the GitHub Martketplace, you can filter by the
Actions Type in the Sidebar.