Repository navigation
docs: clarify directory restrictions for reusable agentic workflows - #71451
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate reusing workflows outside
Oct 23, 2026
.github/workflows/
pelikhan
marked this pull request as ready for review
October 23, 2026 14:41
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The documented cross-repository setup omits requirements needed for successful activation.
2 open issues
What changed in this PR
Clarifies where centrally maintained gh-aw workflows must live to support workflow_call, addressing #71086 without requiring implementation copies in caller repositories.
Changes:
- Distinguishes compilation location from GitHub Actions’ reusable-workflow directory requirements.
- Adds a central
.lock.ymlcaller example. - Explains immutable references, caller access, credentials, and shared imports.
| File | Description |
|---|---|
docs/src/content/docs/reference/faq.md |
Adds an FAQ covering reusable-workflow placement and centralized reuse. |
Review effort: Max
| secrets: inherit | ||
| ``` | ||
|
|
||
| Use a full commit SHA instead of `v1` for an immutable reference. The caller must have access to the reusable workflow and provide the required permissions and engine credentials; `secrets: inherit` is available within the same organization or enterprise. |
|
|
||
| Use a full commit SHA instead of `v1` for an immutable reference. The caller must have access to the reusable workflow and provide the required permissions and engine credentials; `secrets: inherit` is available within the same organization or enterprise. | ||
|
|
||
| For a repository organized by action, keep documentation and shared components separately, but retain the callable entry point in `.github/workflows/`. [Imports](/gh-aw/reference/imports/) can separate shared configuration and prompt content from entry-point Markdown; they are not independently callable workflows. |
Contributor
|
🎉 This pull request is included in a new release. Release: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Central workflow repositories may want Markdown, compiled YAML, and documentation colocated outside
.github/workflows/. GitHub Actions requires callable YAML directly in that directory; gh-aw cannot override this restriction.workflow_calleligibility..lock.ymlwithout copying implementation:.github/workflows/#71086