GitHub Actions

I don't know if that changed, but back in the day, you could only have like one Jenkins file per repo and that was it.

With GitHub Actions, you can actually have multiple pipeline files.

And what usually happens is you would have still someone building those using reusable pipelines from that central repository to do mainline stuff, like the main CI-CD criteria, and then beyond the merge.

But multiple files, multiple CI files in the repository allows teams to add extra files there on top of what's created by the centralized team.

And you need to usually keep the shared library for all of them for the particular instance.

And usually the teams are not too happy about it because they want to have it more customized.

And that's what GitHub Actions gives you.

For example, GitHub Actions gives you much bigger flexibility without influencing everyone with it.

CVE-2026-12537 with CVSS at 10, a solid 10.

Gemini CLI, and this is the numbers, 0.39.1. And the run Gemini CLI GitHub action before 0.1.22.

So Google patched it back in April.

There was a walkthrough at DEF CON, and I'm going to tell you why it was beautiful in a kind of let the world burn type way.

He is a maintainer of Fake Redis, a pure Python implementation of the Redis API that began as a way to write tests without standing up a real server, and now works as a drop-in replacement for both Redis Py and Valkey Py, pulling over 5 million downloads a month.

Beyond Fake Redis, he maintains Django task scheduler, built a GitHub actions plugin for JetBrains IDEs, and helps run Django Commons, a community organization for keeping Django packages healthy.

Welcome, Daniel.

Thank you, and thank you for the nice introduction.

Other than this, I can say that, um, also I had like, uh, two leads, uh, two clients, uh, that, uh, I got thanks to Fake Redis.

They just like approached me.

One of them actually, like, uh, they just saw like what I did with GitHub Action, like implementing this massive matrix [laughs] of like what's going on, and they say like, "Yeah, we need like to do, uh, something similar in our situation, like, uh, with GitHub Actions, and you obviously, like you know how to create like this matrix in GitHub Actions." So yeah, and this, I did the project for them.

Another one, they wanted to extend, uh, actually Fake Redis, so, uh, and have it support, uh, something else.

So after it makes the changes to the files when you run Atmos, you can have it also open a pull request with those changes.

So it works really convenient if you're using GitHub Actions or GitLab.

Actually, GitLab is not supported for opening pull requests.

Another related update is sometimes you need different formats for the version that you update in your files.

And then if I look at this state file migration, this is saying migrate the random pet legacy to random pet service.

And that's why that worked cleanly.

So the beauty with all of this is you can have a fully GitOps-driven approach to migrations that works through your CI-CD process, for example, with GitHub Actions.

And you don't have to apply those migrations locally.

And then I'll be left with a pull request that I can review or whatever.

If it's something open-ended where I'm trying to build the context, like for example, that oxide build kite stuff that I was thinking through, the whole point of that conversation was to flesh out how would this look like? And I would tell the AI agent via voice, I already have a GitHub Actions ephemeral runner.

It works this way.

It uses these APIs.