Same concurrency level is canceling the previous runs

Let’s say I limit the concurrency to 1 job at a time.
If I will push the changes to my PR every 10 sec. According to docs the 'firstis going to beactive, the secondrun will go topending, the third/fourth/fifthwill becanceledbyfifth`.

Do you plan to change this behavior? In my case, I want that all 6 workflows will run sequentially one after the other without canceling the “middle” workflows.

name: Concurrency Test
on:
  pull_request:
jobs:
  concurrency-test:
    concurrency: concurrency-1
    runs-on: ubuntu-latest
    steps:
      - name: Pause for 1 min
        run: |
          sleep 60

3 Likes

Hi is there any update or workaround on this? We have a similar setup and I see no solution for this except to ensure that one workflow is triggered and the next only if the first has finished