Assuming this is just building every example, I wonder if it would be better to have a build-examples.sh (with a e.g. for example_dir in examples/* ...) and just call that from the action?

@lann that definitely takes care of not having to add new examples to the workflow. At first, I was thinking this setup is nice because can use act to run the workflow/build the examples locally which it does in a docker container so you don't have to fumble inconsistent rust/spin environments. If ever something is failing in CI, this setup may make it slightly easier to debug. However, you could have the same exact workflow with a build examples script and the build examples script might even be better if you actually do want to test with your local environment

The only other reason to go this route would be that the github actions output is easy to read and follow (see screenshot below). I can do my best with making the build script pretty though.

Oop sorry I missed your comment @michelleN. It is quite easy to group logs from bash by just printing some magic strings to stdout: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#grouping-log-lines

e.g.

for $dir in examples/*; do
  echo "::group::Building $dir"
  ...
  echo "::endgroup::"
done

sounds good. I'll update and open a new PR