chore(ci): explicit concurrency groups now the shared runner holds 2 slots (#102)
Companion to sow-platform#189 (runner capacity 1 -> 2). Capacity 1 was the implicit mutex serializing every workflow; this makes the exclusions explicit: side-effectful workflows serialized (never cancelled mid-run), PR-triggered checks per-ref with cancel-in-progress.Reviewed-on: #102 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>
This commit was merged in pull request #102.
This commit is contained in:
@@ -7,6 +7,12 @@ on:
|
||||
|
||||
permissions: read-all
|
||||
|
||||
# One run per ref: a new push obsoletes the run on the old head, so cancel it
|
||||
# and free the runner slot for the run that can still matter.
|
||||
concurrency:
|
||||
group: ci-${{ gitea.ref }}
|
||||
cancel-in-progress: true
|
||||
|
||||
jobs:
|
||||
ci:
|
||||
runs-on: nix-docker
|
||||
|
||||
Reference in New Issue
Block a user