Can be used locally by modifying the template_path and executed from outside your local esp-template repo (no cargo command works inside that folder because of the syntax errors in all the files)
Only cover the simplest and more complex cases of options
act is ~not~ working out of the box:
~rust_ci.yml needs to be moved from the .github/workflows/ folder as it fails to parse it due to the weird syntax, again.~
Did some further testing and solved this by moving the rust_ci.yml to a different folder, .github and the on the post-script.rhai move it to the .github/workflows/ if the user accepted the CI prompt. Not very clean, but it allows using act, happy to improve or remove this workaround.
After moving the rust_ci.yml, it works, just make sure you specify the GH TOKEN, required for Xtensa toolchain action: act -s GITHUB_TOKEN="$(gh auth token)" -j verify
Thanks @jessebraham for the ideas to improve the workflow! Any feedback on how to improve it further is more than welcomed!
template_path
and executed from outside your localesp-template
repo (nocargo
command works inside that folder because of the syntax errors in all the files)act
is ~not~ working out of the box:rust_ci.yml
needs to be moved from the.github/workflows/
folder as it fails to parse it due to the weird syntax, again.~rust_ci.yml
to a different folder,.github
and the on thepost-script.rhai
move it to the.github/workflows/
if the user accepted the CI prompt. Not very clean, but it allows usingact
, happy to improve or remove this workaround.rust_ci.yml
, it works, just make sure you specify the GH TOKEN, required for Xtensa toolchain action:act -s GITHUB_TOKEN="$(gh auth token)" -j verify
Thanks @jessebraham for the ideas to improve the workflow! Any feedback on how to improve it further is more than welcomed!