build: Trigger Code-related CI only on Actual Code Changes #795
Description
What is the feature you would like to see?
Triggering the whole CI, including checks, e2e tests etc. makes no sense when:
- CHANGELOG is updated
- only docs are changed
- changes are in ./fuzz/ directory
There are probably other cases, these are just examples.
Instead, CI jobs that test the code should trigger only when the actual code is changed (e.g. changes are in ./contracts/, ./contracts-proc/, ./lib/). There are probably some caveats to this, so we should figure them out.
Addressing this will improve our DevEx, especially during PR reviews when a change request to update wording in CHANGELOG triggers the whole 15-minute CI, which stops us from merging the PR.
Contribution Guidelines
- I agree to follow this project's Contribution Guidelines