Reading up on GitHub Actions
21 deep · digging since nov 26, 25
- Get Started with WarpBuild | $50 in Free Credits
WarpBuild offers faster, cheaper GitHub Actions runners with a one‑line YAML change and $50 free credits for new users today.
- Tests Come for Free Now, and Most of Them Are Pointless - Vincent Schmalbach
AI agents now generate massive test suites automatically, but most add little value; the author trimmed his Laravel project to 63 meaningful tests, reducing runtime from hours to seconds.
- Poisoning a Go Cache
The post demonstrates how manipulating Go's build cache can alter program behavior without source changes, using overlays and cache poisoning to reverse a function's output from true to false.
- Useful Things Agents Can Do That Are Not Writing Code
The author shows how AI agents can automate tasks such as fixing merge conflicts, finding relevant issues, and diagnosing CI failures without writing code.
- Use Speedlify2 to Continuously Measure Website Performance—zachleat.com
Speedlify2 automates continuous website performance measurement for 1565 sites using parallel GitHub Actions runs, decoupled ranking, and more detailed metrics like Core Web Vitals and Axe CLI.
- Home | GitHub Agentic Workflows
GitHub launched Agentic Workflows, which run markdown-defined automation as AI-powered GitHub Actions with sandboxing and spend controls.
- How we built a software factory to drive Astro’s GitHub issue count to zero
Cloudflare and Astro maintainers deployed isolated AI subagents in GitHub Actions to automatically reproduce, diagnose, and verify bugs, cutting open issues from over 200 to ~30 and aiming for zero.
- Your CI should be disposable
The article argues CI should only schedule builds, delegating actual builds to local tools like Docker or Nix so workflows remain runnable even if CI services fail.
- GitHub Actions is the weakest link
GitHub Actions' default features—mutable tags, pull_request_target, template injection, and write-scoped tokens—have enabled a chain of supply-chain attacks on open-source registries, and GitHub's opt-in security roadmap won't fix the root causes.
- GitHub - withastro/flue: The sandbox agent framework.
Flue is a TypeScript framework for building autonomous AI agents with a programmable harness that provides sandboxes, tools, skills, and durable execution across local and cloud runtimes.
- Using skills to accelerate OSS maintenance
Using skills, AGENTS.md, and GitHub Actions, OpenAI accelerated OSS maintenance in their Agents SDK repos, merging 457 PRs in three months, up from 316.
- Perhaps not Boring Technology after all
Current LLM coding agents no longer bias toward popular languages; they handle niche or new tools well via long context and documentation.
- Turn Dependabot off
Dependabot's version-based security alerts are noisy and less effective than static analysis tools that check reachability of vulnerable functions.
- Amplifying — AI Benchmark Research
Claude Code overwhelmingly builds custom solutions over recommending third-party tools, and when it picks tools, it defaults to GitHub Actions, Stripe, and shadcn/ui.
- Insider amnesia
Speculation about internal tech company problems is almost always wrong because outsiders lack the insider context needed to understand the real issues.
- It looks like the status/need-triage label was removed
An unclosed loop in GitHub Actions workflows caused Gemini CLI's label-adding and -removing bots to fight over 4,600 times, flooding the issue with notifications.
- I hate GitHub Actions with passion
GitHub Actions workflows are difficult to debug when they fail inconsistently across platforms due to runner setup differences, and the author recommends keeping logic in local scripts.
- Pricing Changes for GitHub Actions
GitHub backtracks on a per-minute platform fee for self-hosted Action runners after heavy backlash, while cutting hosted-runner prices by up to 39%.
- What They Don't Tell You About Maintaining an Open Source Project ~ andrej acevski
Maintaining an open-source self-hosted kanban board involves relentless documentation, user support, scary database migrations, and careful scope management far beyond building the initial product.