[Github] Cancel previous in-progress code formatting jobs

[boomanaiden154]

If the user pushes multiple times in relatively rapid succession, we might end up with multiple code formatting jobs in flight at the same time for different revisions of the same PR. It makes no sense to keep jobs running on outdated versions of the PR.

Additionally, if my hypothesis proves correct, this might end up fixing

[llvmbot]

@llvm/pr-subscribers-github-workflow

Author: Aiden Grossman (boomanaiden154)

Changes

If the user pushes multiple times in relatively rapid succession, we might end up with multiple code formatting jobs in flight at the same time for different revisions of the same PR. It makes no sense to keep jobs running on outdated versions of the PR.

Additionally, if my hypothesis proves correct, this might end up fixing

---

Full diff: https://github.com/llvm/llvm-project/pull/106701.diff

1 Files Affected:

• (modified) .github/workflows/pr-code-format.yml (+3)

diff --git a/.github/workflows/pr-code-format.yml b/.github/workflows/pr-code-format.yml
index 1a1700b75cfdb7..f2bb37316d3a8b 100644
--- a/.github/workflows/pr-code-format.yml
+++ b/.github/workflows/pr-code-format.yml
@@ -13,6 +13,9 @@ jobs:
   code_formatter:
     runs-on: ubuntu-latest
     timeout-minutes: 30
+    concurrency:
+      group: ${{ github.workflow }}-${{ github.event.pull_request.number }}
+      cancel-in-progress: true
     if: github.repository == 'llvm/llvm-project'
     steps:
       - name: Fetch LLVM sources

[boomanaiden154]

CC @nicovank

This doesn't replace the need to get rid of the checkout through merge base step in this workflow, but if this actually fixes the underlying timeout issue, that turns into an optimization rather than a correctness issue.

Once this lands, I'll monitor the run time of the PR code format job to see if there are any new timeouts to confirm if we've fixed it or not.