Test out running github actions locally for speed

[stan-dot]

if this tool turns out easy to configure it would be great https://github.com/nektos/act

[callumforrester]

Does this issue require any code changes in this repository?

[stan-dot]

possibly, many tools allow for custom configuration with a config file.
otherwise adding a line to install the tool into .devcontainer might be pursued

not sure what ask this question now @callumforrester

it's an implementation detail - the issue is about the dev hours cost-benefit analysis - if we invest a a chunk of time now, what would be the future time saving stream of benefits (and possibly a stream of costs to keep it)

[callumforrester]

Okay, well since you raised the issue, please could you outline the pros and cons (i.e. more detail than the current PR description). Otherwise I will close it.

[stan-dot]

the issue IS to gather those pros and cons. this is not a PR, this is just a vague issue chucked into the backlog, to be considered on a per-sprint basis

[vredchenko]

act looks interesting - have not heard of it before. There's another tool that might be worth looking at: https://dagger.io/ I don't have prior experience with it, but at first glance the difference is that act takes an existing Github workflow and runs it locally whereas dagger approach is to write out the scripts using "Dagger Functions" and then run them anywhere (so act sounds like less work, but need to investigate a bit more).