Max Cascone
Max Cascone
I literally don't remember opening this issue π³
CLI could be cool, or you could add the option to point to a local repo in the UI. The docs to run it locally are good*, I've got it...
All I want is to be able to develop my actions locally, separate from the repo with the workflow file that calls them. Specifically, I want to be able to...
is there any documentation on this other than the help text? ``` --local-repository stringArray Replaces the specified repository and ref with a local folder e.g. https://github.com/test/test@v0=/home/act/test or test/test@v0=/home/act/test, the latter...
`act` images don't include some very basic tools, including `gh`, `jq`, `gcloud cli`, etc. You can pull the much larger `catthehacker` images, or install just what you need on local...
Stuff like this: ``` π³ docker exec cmd=[/usr/local/bin/node /var/run/act/actions/actions-checkout@v4/dist/index.js] user= workdir= [init] π¬ ::debug::Getting git version | [command]/usr/bin/git version | git version 2.20.1 [init] π¬ ::debug::0 [init] π¬ ::debug::git version...
yeah, I'd like to not see the docker commands too, but they're less annoying than the `::debug::` lines. You mentioned your patch, and I see the commit - how do...
> @mcascone Try act -q. Doesn't that quiet all stdout, including echoes to the console? Thatβs not really what weβre after. I could be wrong!
> Sample output with act -q: I still get very noisy output with `-q`: ``` [init] π¬ ::debug::Getting git version [init] π¬ ::debug::0 [init] π¬ ::debug:: [init] π¬ ::debug::0 [init]...
@ggascoigne Do you happen to be running behind a corporate firewall? I think that's the reason for my failures. Well, the ones occurring when running this cli, at least :)