Lots of fun projects being listed. I'm working on Preloop(https://preloop.dev), a way to run your unmodified Github Actions locally or self-hosted in isolated cross-platform microvms(uses smolvm which uses libkrun vmm).I got frustrated with Github Actions reliability and inability to run or test my workflows locally so i re-wrote the runner and reverse-engineered the control plane so it follows the exact runner protocol the offficial runner does. Each job runs in a microvm that boots in 400ms from a packed image. Also supports a way to pause on every failure so you or your agent can immediately shell at that point, fix and retry(in a new environment) to verify. Also supports the full DAP protocol so you can interactively step/forward/investigate context at each step/job.
a bold attempt, how does it compare with https://github.com/nektos/act which has been the de-jure project in this space? Act has never been in my opinion super great, but it's also been several years since I've checked in to revisit the project.
Thanks! Here's a more detailed comparison: https://github.com/preloopdev/preloop/blob/main/docs/preloop.... The TLDR is act(much like Forgejo/Gitea) try to behaviorally emulate how your workflows run in docker containers. Preloop uses the exact same protocol the official runner does and runs each job in microvms. I try to match not only te request/response bodies, but down to the job/step log/annotations/conclusions level, so you could essentially use the official runner against preloop, and it would work as it would communicating with Github. Preloop is also designed to be agent-native from the ground up so an agent can drive the entire CI in real-time and debug like we do. Forgejo has the closest compatibility among the three in practice, and if you are fully off Github, I think it's a good enough choice. Here's a more detailed description of some things we do to ensure compatibility: https://github.com/preloopdev/preloop/blob/main/docs/conform...
Yes! You could effectively use the official runner against preloop or our (almost) drop-in rust equivalent which is a 10x smaller binary and has far lower idle rss. The control plane currently is unfortunately coupled with the data plane, but a refactor is one of my top priorities soon.
That is an amazing idea. I can imagine this getting popular. It could be used for faster local dev loops and porting GHA to other servers. I imagine for data/compute residency, cost, performance, vm types etc.
Thanks! I'm glad it resonates. Still pretty beta, but I'm hoping this can be a good alternative when Github goes down, which unfortunately has been a bit too often, with as minimal of a lift from the user side. And of course, making it easier for agents to fully drive ci.
thanks for the feedback! Was it mostly the font, structure or content or everything? I’ll make sure to use a more minimal/standard docs site. For now I have them in /docs in the repo.
the font is pretty small plus its not pleasing to read and get info from, the sections should be made bigger to indicate its a section or maybe not even the size some sort of indicator should be there. plus the text near "AGENT LOOP" that goes vertically is hindering with the existing text
I just wanted to chime in and offer an additional datapoint.
I also think the project is cool but the font on the site is a bit hard to read as is. I like the brutalist / minimalist nature of it. It's an attractive design, but the font is a narrow font with low spacing between characters (Berkeley mono?) and when you have a font like that it makes it 'feel' harder to read. If you are dead set on that font, and it does seem like an intentional design choice, you could improve contrast a bit by brightening up the text, an increase the size a bit as well. you do have plenty of negative space on the page to work with. so the extra size wouldn't be to problematic for you.
Try it out: https://github.com/preloopdev/preloop