3 ms·

Whilst you're waiting for it to come back, try out AGENT-CI (which is a project I built.), which runs GitHub Actions on your machine: https://agent-ci.dev https

Whilst you're waiting for it to come back, try out AGENT-CI (which is a project I built.), which runs GitHub Actions on your machine: https://agent-ci.dev https://agent-ci.dev. (Open source, etc.) No, it's not like "act," because it uses the standard Github runner, the difference is that the control plane is an emulation of api.github.com, because of this we can do all kinds of nice things: Caching in ~0 ms. Pause on failure, so you can let your AI agent fix it and retry without pushing.

ramon156 4mo ago
"Its not like act, because we can add AI" Is what it boils down to. > codex "Fix this pipeline, use `act` to verify your changes"
- Xirdus 4mo ago
  I had extremely bad experience trying to setup act on my Macbook. If this is something that actually works (and doesn't steal my credentials), I'm willing to try it despite AI non-features.
  - Groxx 4mo ago
    Yea, I've had only barely-success on only a few projects with act. Usually due to steps/scripts that use github-internal APIs, but afaict far from always. I like that it exists, but what a freaking mess that it's necessary and so difficult to do.
    - pistoriusp 4mo ago
      Please try agent-ci; it's github actions that run locally. Nothing less.
- pistoriusp 4mo ago
  I did not say that, what I said was: It's not like `act` because it's not a rewrite of the runner. It's the standard runner... So the one that actually runs GitHub Actions. I have tried to use act many times, and many times I've failed. P.S. pause on failure is also helpful for humans, but I'm trying to be realistic about where the future of programming is going...
a1o 4mo ago
What I don’t get about this is how you run OS specific tasks (Windows, macOS, Linux).. I started playing with proxmox VMs and containers in them (docker and tart) to see if I can build some local infrastructure to properly solve this…
- pistoriusp 4mo ago
  We support macOS via tartlet, but basically it's always linux. If you need windows then it's gonna be an issue. The jobs runs via containers.
skinfaxi 4mo ago
You're affiliated with the project. You should definitely be upfront about that when shilling.
- pistoriusp 4mo ago
  You're right, figured it was implied, but now fixed.

ramon156 4mo ago

"Its not like act, because we can add AI" Is what it boils down to. > codex "Fix this pipeline, use `act` to verify your changes"

Xirdus 4mo ago
I had extremely bad experience trying to setup act on my Macbook. If this is something that actually works (and doesn't steal my credentials), I'm willing to try it despite AI non-features.
- Groxx 4mo ago
  Yea, I've had only barely-success on only a few projects with act. Usually due to steps/scripts that use github-internal APIs, but afaict far from always. I like that it exists, but what a freaking mess that it's necessary and so difficult to do.
  - pistoriusp 4mo ago
    Please try agent-ci; it's github actions that run locally. Nothing less.
pistoriusp 4mo ago
I did not say that, what I said was: It's not like `act` because it's not a rewrite of the runner. It's the standard runner... So the one that actually runs GitHub Actions. I have tried to use act many times, and many times I've failed. P.S. pause on failure is also helpful for humans, but I'm trying to be realistic about where the future of programming is going...

a1o 4mo ago

What I don’t get about this is how you run OS specific tasks (Windows, macOS, Linux).. I started playing with proxmox VMs and containers in them (docker and tart) to see if I can build some local infrastructure to properly solve this…

pistoriusp 4mo ago
We support macOS via tartlet, but basically it's always linux. If you need windows then it's gonna be an issue. The jobs runs via containers.

skinfaxi 4mo ago

You're affiliated with the project. You should definitely be upfront about that when shilling.

pistoriusp 4mo ago
You're right, figured it was implied, but now fixed.