Kyle Harding
Kyle Harding
@ab77 I don't think this issue is urgent, just something I was thinking about. If we added `all_test` and `all_publish` jobs as described [here](https://github.com/product-os/flowzone/issues/195#issuecomment-1241352749) using the same conditional logic as...
In this case we wouldn't do any build/test/finalize steps, just the versioning?
An example of this being done for the handbook is here: https://github.com/balenaltd/handbook/tree/50b6c0d9fef1a2a45138fb6869fa8e61103dec5e/.github/actions
The current calculation is putting a lot of devices over the limit ``` HUP size check failed: docker image (249856 KiB) + /boot volume (28672 KiB) = 278528 KiB exceeds...
I think we could resolve this by making at least one engines check a requirement, with no fallback. We would have to update some repos that do not currently specify...
We are using an action in the npm finalize job that allows copying artifacts between workflows which would be required for this. On Mon, Sept 19, 2022, 8:12 a.m. fisehara...
But then the custom steps/jobs don't get to benefit from the versioned source provided by Flowzone? If they don't share artifacts there is no need for any change to Flowzone....
An alternative would be [ACT](https://github.com/nektos/act) or other github action workflow simulators. However ACT does [not currently work with reusable workflows](https://github.com/nektos/act/issues/826).
cc @20k-ultra