GitHub Actions OIDC for Python That Just Works(TM)

Run any GitHub repository in the click of a button

From git clone to running code in one command

Hi everyone! I just released the Practical Python Projects book! (https://practicalpython.yasoob.me) I am happy to announce the first version as a release candidate. I have poured a lot of love into writing this book and would love to hear what you guys think. (A limited 100% off and discount coupons at the end) This is not a pure beginner book. The book does assume some background Python knowledge. You need to know the basics like methods, functions, classes, and such. If I use something that is not typically covered in beginner Python books, I will explain it before I use it.…

Hi all! I wanted to share a small project that I've been working on with a buddy. https://www.actionspanel.app/ One of the problems that currently exists with GitHub Actions is the fact that there is no way to easily trigger your Actions unless you cause some kind of GitHub event. This could be pushing a new commit, or creating an issue on a repository. But if you just want to run an arbitrary action, there's not currently a good way to do that. This is a well known feature request: https://github.community/t5/GitHub-Actions/GitHub-Actions-Ma... GitHub…

We're two engineers that got fed up with context switching. Why do we need to do a git push, open a browser tab, wait for some task to actually start, bite nails (or read HackerNews) for 10 minutes or more while dependencies are being installed for the 100th time and finally end up with an invalid YAML error. And for some reason this usually happens in the final stage of the pipeline leading up to the inevitable git commits "Fixed", "Fixed again", "Test", "Really fixed this time". We can do better. We set out to build Zippy. A CI/CD system that works from your terminal. No context…

I spend a lot of my time writing GitHub Actions. Specifically, I need to script a ton of things. The current way of writing GitHub Actions with YAML is usually fine for small jobs. But for anything complicated, I often find myself in incredibly cursed "shell-in-YAML" situations. This was a major source of bugs for me. Since the "script" was written in YAML, there was actually not an easy way to modularize out the scripting logic to unit test them. Worse, there was zero type safety! For those who work with GitHub Actions frequently, you know how annoying this gets. My ideal GitHub Actions…