From 59edee0f406bb842f2dbbc523fa366f927178ed9 Mon Sep 17 00:00:00 2001 From: Martin Helmich Date: Tue, 17 Oct 2023 11:57:27 +0200 Subject: [PATCH] Only "deploy" job should be concurrency-controlled --- .github/workflows/docusaurus.yml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/workflows/docusaurus.yml b/.github/workflows/docusaurus.yml index ccd58903..703d5342 100644 --- a/.github/workflows/docusaurus.yml +++ b/.github/workflows/docusaurus.yml @@ -9,12 +9,6 @@ on: # Allows you to run this workflow manually from the Actions tab workflow_dispatch: -# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued. -# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete. -concurrency: - group: "deploy" - cancel-in-progress: false - jobs: # Build job build: @@ -50,6 +44,12 @@ jobs: # Deployment job deploy: + # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued. + # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete. + concurrency: + group: "deploy" + cancel-in-progress: false + environment: name: production url: https://developer.mittwald.de