News for hackers. Stuff that matters.
Re:Any program can be a GitHub Actions shell by dharmab on Tuesday April 08, 2025 @03:48AM (#43619328)
- you have an automatic, managed GitHub API token which is useful for automating releases and publishing artifacts and containers

- if your software is cross platform you can run jobs across a variety of OSes and CPU architectures concurrently, e.g. building and testing natively on all platforms

- you have access to a lot of contextual information about what triggered the job and the current state of the repo, which is handy for automating per-PR chores or release automation

- You can integrate some things into the GitHub Web UI, such as having your linter annotate the PR line-by-line with flagged problems, or rendering test failures in the web page so you don't have to scan through a long log for them

- You have a small cache you can use to avoid redownloading/rebuilding files that have not changed between builds

Ideally you do as much as possible in a regular tool that runs locally (make/scripts/whatever) and you use the GitHub CI config for the little bit of glue that you need for the triggers, caching and GitHub integrations

There are no comments on this comment yet.