Closed gouttegd closed 1 year ago
Test suite run explicitly cancelled since the change in build-and-test.yml
does not touch the test suite itself – only when it is triggered. This is not a change affecting anything the CI check can test.
See this comment for more details on the rationale for re-enabling automatic triggering of the test suite.
Update the configuration of the main CI workflow to trigger a CI check not only when a PR is initially opened, but also when new commits are pushed to it ("synchronize" event).
The reason for not triggering new CI checks when a PR is updated was to avoid too many runs of the test suite, but this was before we added a path-based ignore rule that prevents the test suite from being run on changes that do not affect any running code. With such a rule in place, avoiding automatically triggered CI checks is no longer warranted.