-
Notifications
You must be signed in to change notification settings - Fork 307
[docs] Self-healing documentation fixes from issue analysis - 2026-03-20 #22020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -1343,10 +1343,12 @@ safe-outputs: | |||||
|
|
||||||
| Most safe outputs support cross-repository operations: | ||||||
|
|
||||||
| - **`target-repo`**: Set a default target repository for all operations of this type | ||||||
| - **`allowed-repos`**: Allow the agent to dynamically choose which repository to target (from an allowlist) | ||||||
| - **`target-repo`**: Set a fixed target repository (`owner/repo` format), or use `"*"` as a wildcard to let the agent supply any repository at runtime. | ||||||
| - **`allowed-repos`**: Allow the agent to dynamically choose from an allowlist of repositories (supports glob patterns, e.g. `org/*`). | ||||||
|
|
||||||
| See [Cross-Repository Operations](/gh-aw/reference/cross-repository/) technical details. | ||||||
| Using `target-repo: "*"` enables fully dynamic routing — the agent provides the `repo` field in each tool call. Note that `create-pull-request-review-comment`, `reply-to-pull-request-review-comment`, `submit-pull-request-review`, `create-agent-session`, and `manage-project-items` do not support the wildcard; use an explicit repository or `allowed-repos` for those types. | ||||||
|
||||||
| Using `target-repo: "*"` enables fully dynamic routing — the agent provides the `repo` field in each tool call. Note that `create-pull-request-review-comment`, `reply-to-pull-request-review-comment`, `submit-pull-request-review`, `create-agent-session`, and `manage-project-items` do not support the wildcard; use an explicit repository or `allowed-repos` for those types. | |
| Using `target-repo: "*"` enables fully dynamic routing — the agent provides the `repo` field in each tool call. Note that `create-pull-request-review-comment`, `reply-to-pull-request-review-comment`, `submit-pull-request-review`, `create-agent-session`, and `update-project` do not support the wildcard; use an explicit repository or `allowed-repos` for those types. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
manage-project-itemsis referenced here as a safe-output type that doesn’t supporttarget-repo: "*", but it doesn’t appear to exist anywhere else in the repository (no code/docs/schema matches). This likely should refer to an actual safe output type that rejects wildcards (e.g.,update-projectuses wildcard-disallowing parsing) or the item should be removed to avoid documenting a non-existent feature.