At the moment, pushing commits to a PR where GitHub Actions CI is alreaady running does not cancel the running job. Instead, the job continues running and a new job is scheduled. This is unnecessarily wasteful and adds delays to the time CI takes on our PRs.
It looks like GitHub Actions concurrency is the answer to this problem. We need to include the following in our jobs -
concurrency:
# These lines should have the effect of cancelling CI runs for
# existing commits when a new commit is pushed to the PR.
group: ${{ github.head_ref }}
cancel-in-progress: true
At the moment, pushing commits to a PR where GitHub Actions CI is alreaady running does not cancel the running job. Instead, the job continues running and a new job is scheduled. This is unnecessarily wasteful and adds delays to the time CI takes on our PRs.
It looks like GitHub Actions concurrency is the answer to this problem. We need to include the following in our jobs -