In our https://github.com/easybuilders/easybuild-easyconfigs repository, CI tests for pull requests sometimes (rightfully) fail when the PR depends on a change made in another PR.
When we were (only) using Travis CI, it was simple to re-trigger the tests by closing & re-opening the PR when the other PR it requires got merged. This triggered a new test run in Travis CI, effectively discarding the old result for the last commit in the PR.
Now that we’re (also) usign Github Actions CI, closing & re-opening a pull request also triggers a new suite of test runs, but the old runs stay there , and hence the status of the last commit in the PR will be still be failure, even if all the new GitHub Actions CI runs pass.
How can we avoid that old GitHub CI runs are taken into account to determine the status of pull requests?
Can we discard old runs somehow if we know they’re no longer relevant?