Any program can be a GitHub Actions shell(yossarian.net) In GitHub Actions, you can use the shell keyword to specify the shell that runs a given run: block. This keyword is optional for workflows but mandatory for action definitions.
282 points by woodruffw 18 days ago | 101 comments
Disk I/O bottlenecks in GitHub Actions(depot.dev) When your CI pipelines are slow, you can only optimize so much. Bottlenecks in CPU, Network, Memory, and Disk I/O can all contribute to slow CI pipelines. Let's take a look at how disk I/O can be a bottleneck in GitHub Actions.
Solving the Pain that is CI/CD(dan-manges.com) Last week, The Pain That Is GitHub Actions was on the front page of Hacker News. It received 700 upvotes and 500+ comments. The pain is widespread, and opinions on how to solve it are highly varied.
Ollama Models Atom Feed(simonwillison.net) simonw/ollama-models-atom-feed. I setup a GitHub Actions + GitHub Pages Atom feed of scraped recent models data from the Ollama latest models page - Ollama remains one of the easiest ways to run models on a laptop so a new model release from them is worth hearing about.
Show HN: Sticky Disks in GitHub Actions(github.com/useblacksmith) A GitHub Action that helps persist state written to disk across jobs. This action can serve as a superior alternative to the Actions cache, especially when the cache artifacts are extremely large. Each sticky disk is hot-loaded into the runner and mounted at the specified path.
The sticky disk is formatted as an ext4 filesystem.