How GitHub Actions is different to traditional build servers
Blog post from Octopus Deploy
GitHub Actions, an integrated CI as a Service within GitHub, offers a streamlined approach to continuous integration by eliminating the need for separate build servers and reducing infrastructure maintenance. It utilizes runners, which are GitHub-hosted virtual machines, to execute workflows triggered by events in a repository or external webhooks, allowing flexibility in automation. The service is particularly advantageous for users already on GitHub, as it provides a cohesive environment with fewer components to manage. Pricing is based on a pay-as-you-go model, offering free monthly minutes and storage, with additional charges based on usage. While GitHub Actions is not suitable for those using other code repositories, it does provide a vast array of community-made actions and workflows via the GitHub Marketplace, simplifying the setup process. The installation of actions involves copying code into a repository's .yml file, which enhances functionality without altering the user interface.