[docs] Update glossary - daily scan 2026-03-05#19712
Conversation
Add CentralRepoOps, Trigger File, workflow_call, and Conclusion Job terms. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the documentation glossary to reflect newly documented patterns and workflow features added in recent docs changes (CentralRepoOps trigger file + workflow_call pattern, and conclusion job concurrency behavior).
Changes:
- Adds glossary entries for Trigger File and workflow_call tied to the CentralRepoOps trigger-file pattern.
- Adds a glossary entry for Conclusion Job referencing automatic concurrency behavior.
- Adds a glossary entry for CentralRepoOps as an operational pattern variant of MultiRepoOps.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
|
|
||
| ### Conclusion Job | ||
|
|
||
| An automatically generated job in compiled workflows that handles post-agent reporting and cleanup. Receives a workflow-specific concurrency group (`gh-aw-conclusion-{workflow-name}`) to prevent collision when multiple agent instances run the same workflow concurrently. Requires no manual configuration — the compiler sets the group automatically. See [Concurrency Control](/gh-aw/reference/concurrency/). |
There was a problem hiding this comment.
The Conclusion Job concurrency group name here doesn’t match the compiler behavior or the Concurrency Control reference. The group is derived from the workflow ID/filename (see docs/reference/concurrency.md and pkg/workflow/notify_comment.go where it’s built from WorkflowID), so gh-aw-conclusion-{workflow-name} is misleading. Please update this to reflect the workflow ID/filename placeholder and keep placeholder formatting consistent with other glossary entries.
| An automatically generated job in compiled workflows that handles post-agent reporting and cleanup. Receives a workflow-specific concurrency group (`gh-aw-conclusion-{workflow-name}`) to prevent collision when multiple agent instances run the same workflow concurrently. Requires no manual configuration — the compiler sets the group automatically. See [Concurrency Control](/gh-aw/reference/concurrency/). | |
| An automatically generated job in compiled workflows that handles post-agent reporting and cleanup. Receives a workflow-specific concurrency group (for example, `gh-aw-conclusion-{workflow-id}` derived from the workflow file name/ID) to prevent collision when multiple agent instances run the same workflow concurrently. Requires no manual configuration — the compiler sets the group automatically. See [Concurrency Control](/gh-aw/reference/concurrency/). |
|
|
||
| ### Trigger File | ||
|
|
||
| A plain GitHub Actions workflow (`.yml`) that separates trigger definitions from agentic workflow logic. Calls a compiled orchestrator's `workflow_call` entry point in response to any GitHub event (issues, pushes, labels, manual dispatch). Decouples trigger changes from the compilation cycle — updating when an orchestrator runs requires editing only the trigger file, not recompiling the agentic workflow. See [CentralRepoOps](/gh-aw/patterns/central-repo-ops/). |
There was a problem hiding this comment.
In GitHub Actions, “labels” aren’t a top-level workflow trigger; label-based runs are typically issues/pull_request events with types: [labeled]. Consider rephrasing this parenthetical to avoid implying labels is its own event (e.g., “issue/PR label events”).
| A plain GitHub Actions workflow (`.yml`) that separates trigger definitions from agentic workflow logic. Calls a compiled orchestrator's `workflow_call` entry point in response to any GitHub event (issues, pushes, labels, manual dispatch). Decouples trigger changes from the compilation cycle — updating when an orchestrator runs requires editing only the trigger file, not recompiling the agentic workflow. See [CentralRepoOps](/gh-aw/patterns/central-repo-ops/). | |
| A plain GitHub Actions workflow (`.yml`) that separates trigger definitions from agentic workflow logic. Calls a compiled orchestrator's `workflow_call` entry point in response to any GitHub event (issues, pushes, issue/PR label events, manual dispatch). Decouples trigger changes from the compilation cycle — updating when an orchestrator runs requires editing only the trigger file, not recompiling the agentic workflow. See [CentralRepoOps](/gh-aw/patterns/central-repo-ops/). |
Glossary Updates - 2026-03-05
Scan Type
Terms Added
a0ed2f4). A MultiRepoOps variant using a single private repo as a control plane for large-scale cross-repository operations..ymlworkflow that separates trigger definitions from agentic workflow logic viaworkflow_call.39cf121).Changes Analyzed
a0ed2f4adding trigger file + workflow_call pattern to CentralRepoOps39cf121adding Conclusion Job concurrency sectionRelated Changes
a0ed2f4: docs: add trigger file + workflow_call pattern to CentralRepoOps (docs: add trigger file + workflow_call pattern to CentralRepoOps #19693)39cf121: [docs] Update documentation for features from 2026-03-05 ([docs] Update documentation for features from 2026-03-05 #19690) — adds Conclusion Job concurrency docs