GitHub Actions
CI that runs the same checks a developer runs locally.
- made by
- GitHub
Magic Ship is one shop in Vancouver, BC, working remotely with clients worldwide. We are not a partner, reseller, or certified vendor of GitHub - we just build with this.
What GitHub Actions is
GitHub Actions runs workflows on hosted or self-hosted runners in response to pushes, pull requests, schedules, and manual triggers. Jobs run in containers or VMs, can fan out across a version matrix, and take secrets from the repository or organisation. It is usually where deploys are triggered from as well.
How we use it
We put one command behind CI - the same command a developer runs locally - so there is never a check that only exists on the server. On AI projects the eval suite runs there against a pinned model id, and a regression on the golden question set fails the build like any other test. Deploys run from a workflow holding the environment's credentials, never from somebody's laptop.
Where it is the wrong choice
Hosted runners are slow for heavy builds and cannot see a private network, so a client with self-hosted infrastructure needs self-hosted runners and the upkeep that comes with them. Full eval suites also get expensive on every push, so we gate the long ones behind a label or a schedule.
Service lines it turns up in
Related tools
More in Infrastructure and deploy
Other tools in the same service lines
Building something on GitHub Actions?
Send the problem rather than a job spec. You get an answer on scope, on fit, and on whetherGitHub Actions is even the right call for it.
Start a projectGitHub Actions and GitHub are trademarks of their respective owners, used here to say what we work with.