Closed cisaacstern closed 1 week ago
A possibly helpful design reference https://pixi.sh/dev/advanced/updates_github_actions/
This is related but not the exact same use case, as I am thinking of commits to active PRs, not new PRs. Though the latter may be what we are after for the ecoscope-platform-workflows-releases
version of this.
Developers should need to recompile workflows manually.
Let's do that for them (ourselves) with a GitHub workflow that functions something like precommit.ci.
When certain files change, e.g. the compiler / artifacts logic, examples/spec.yaml or examples/test-cases.yaml, etc., then we can have a Github Workflow re-compile and push those changes as a commit on the back of the developer's changes. This could be disabled by a PR label flag or similar.