From ef96520e93b2d33f385bff0db917c05ecfd2ab14 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 5 Mar 2026 04:23:06 +0000 Subject: [PATCH 1/2] docs: document conclusion job concurrency group Add a new section to the Concurrency Control reference explaining that the `conclusion` job automatically receives a workflow-specific concurrency group (`gh-aw-conclusion-{workflow_id}`) during compilation. This prevents conclusion jobs from colliding when multiple agents run the same workflow concurrently. Co-Authored-By: Claude Sonnet 4.6 --- docs/src/content/docs/reference/concurrency.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/src/content/docs/reference/concurrency.md b/docs/src/content/docs/reference/concurrency.md index edda4cf988a..27455b24062 100644 --- a/docs/src/content/docs/reference/concurrency.md +++ b/docs/src/content/docs/reference/concurrency.md @@ -67,6 +67,21 @@ When set, the `safe_outputs` job uses `cancel-in-progress: false` — meaning qu See [Safe Outputs](/gh-aw/reference/safe-outputs/#safe-outputs-job-concurrency-concurrency-group) for details. +## Conclusion Job Concurrency + +The `conclusion` job — which handles reporting and post-agent cleanup — automatically receives a workflow-specific concurrency group derived from the workflow filename: + +```yaml wrap +conclusion: + concurrency: + group: "gh-aw-conclusion-my-workflow" + cancel-in-progress: false +``` + +This prevents conclusion jobs from colliding when multiple agents run the same workflow concurrently. The group uses `cancel-in-progress: false` so queued conclusion runs complete in order rather than being discarded. + +This concurrency group is set automatically during compilation and requires no manual configuration. + ## Related Documentation - [AI Engines](/gh-aw/reference/engines/) - Engine configuration and capabilities From 6d455e8898545b4b682d5b9ec480f6f56b30c09a Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Thu, 5 Mar 2026 04:24:57 +0000 Subject: [PATCH 2/2] ci: trigger checks