From 65b085ba3b0cedf1670fd0a3dc83651d0235cce2 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 3 Jun 2026 12:20:57 +0000 Subject: [PATCH 1/2] docs: update glossary with max-turns and force-clean-git-credentials (#36629) From 0a96965175c0a46e5118ab939d2e55c6b1153f9c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 3 Jun 2026 12:20:59 +0000 Subject: [PATCH 2/2] docs: document aw.yml license field and submit-pull-request-review target - Add `license` field to the repository package manifest specification (table row + section), matching the schema field added in #36583. - Document the `pull_request_number`/`repo` requirement for submit-pull-request-review when target: "*", matching the support added in #36546. Co-Authored-By: Claude Opus 4.8 (1M context) --- .../reference/repository-package-manifest-specification.md | 7 ++++++- .../content/docs/reference/safe-outputs-pull-requests.md | 2 ++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/src/content/docs/reference/repository-package-manifest-specification.md b/docs/src/content/docs/reference/repository-package-manifest-specification.md index 91a820da3bb..3844c9eacee 100644 --- a/docs/src/content/docs/reference/repository-package-manifest-specification.md +++ b/docs/src/content/docs/reference/repository-package-manifest-specification.md @@ -46,6 +46,7 @@ The manifest document MUST be a YAML mapping. Unknown top-level fields MUST be r | `name` | string | Yes | Human-readable package name. | | `emoji` | string | No | Optional package emoji for display in package metadata. | | `description` | string | No | Human-readable package description. | +| `license` | string | No | SPDX license identifier or license name for the package. | | `files` | array of strings | No | Explicit installable workflow file list. | ### 4.2 `manifest-version` @@ -76,7 +77,11 @@ If present, `description` MUST be a string. Implementations SHOULD warn if `description` exceeds 255 characters. -### 4.7 `files` +### 4.7 `license` + +If present, `license` MUST be a string. Use an [SPDX license identifier](https://spdx.org/licenses/) such as `MIT` or `Apache-2.0`, or a license name. Non-string values MUST be rejected. + +### 4.8 `files` If present, `files` MUST be an array of strings. diff --git a/docs/src/content/docs/reference/safe-outputs-pull-requests.md b/docs/src/content/docs/reference/safe-outputs-pull-requests.md index fdcf2c1f519..fa9fb0a38c9 100644 --- a/docs/src/content/docs/reference/safe-outputs-pull-requests.md +++ b/docs/src/content/docs/reference/safe-outputs-pull-requests.md @@ -186,6 +186,8 @@ Use `allowed-events` to control review decisions (`APPROVE`, `COMMENT`, `REQUEST When you intentionally allow `REQUEST_CHANGES`, set `supersede-older-reviews: true` to dismiss older blocking reviews from the same workflow after posting a replacement review. This behavior is best-effort. +When `target: "*"` is configured, the agent must supply `pull_request_number` in each `submit_pull_request_review` tool call to identify which PR to review — omitting it will cause the review to fail. For cross-repository scenarios, the agent can also supply `repo` (in `owner/repo` format) to route the review to a PR in a different repository; the value must match `target-repo` or appear in `allowed-repos`. + ## Reply to PR Review Comment (`reply-to-pull-request-review-comment:`) Replies to existing review comments on pull requests. Use this to respond to reviewer feedback, answer questions, or acknowledge comments. The `comment_id` must be the numeric ID of an existing review comment.