Splits our github Pull Request workflow into one per module, so that we can run jobs only when code changes.
Resolves #847
Notes
All these improvements will speed up our PR checks, and also potentially reduce our costs:
Sparse checkout, only fetch the code needed to run a job
Run job only on related code changes, e.g. no need to run frontend code checks if PR only has backend code changes
Run build/test in parallel with lint/format checks
Concerns
These checks will not run until they are in dev branch, so they won't run on this PR. I don't think we can even trigger them manually yet, as if I recall, they don't appear in the github Actions tab until they are in dev. So, we won't be able to test the new jobs until we start opening subsequent PRs.... 🍀
Description
Splits our github Pull Request workflow into one per module, so that we can run jobs only when code changes.
Resolves #847
Notes
All these improvements will speed up our PR checks, and also potentially reduce our costs:
Concerns
Checklist
Have you done the following?