From c70aab4e34086e86be15e8b0ba89f1e5ccd6c883 Mon Sep 17 00:00:00 2001 From: "Claude Sonnet 4.5" Date: Fri, 23 Jan 2026 20:32:25 +0000 Subject: [PATCH] Add remove-labels safe-output documentation to instructions - Document remove-labels safe-output type - Include configuration schema with allowed, max, target, and target-repo fields - Document permission separation pattern - Position after add-labels for logical grouping Sync with v0.36.0 release documentation. --- .github/aw/github-agentic-workflows.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/.github/aw/github-agentic-workflows.md b/.github/aw/github-agentic-workflows.md index 92507160258..07246086090 100644 --- a/.github/aw/github-agentic-workflows.md +++ b/.github/aw/github-agentic-workflows.md @@ -465,6 +465,16 @@ The YAML frontmatter supports these fields: target-repo: "owner/repo" # Optional: cross-repository ``` When using `safe-outputs.add-labels`, the main job does **not** need `issues: write` or `pull-requests: write` permission since label addition is handled by a separate job with appropriate permissions. + - `remove-labels:` - Safe label removal from issues or PRs + ```yaml + safe-outputs: + remove-labels: + allowed: [automated, stale] # Optional: restrict to specific labels + max: 3 # Optional: maximum number of operations (default: 3) + target: "*" # Optional: "triggering" (default), "*" (any issue/PR), or number + target-repo: "owner/repo" # Optional: cross-repository + ``` + When `allowed` is omitted, any labels can be removed. Use `allowed` to restrict removal to specific labels. When using `safe-outputs.remove-labels`, the main job does **not** need `issues: write` or `pull-requests: write` permission since label removal is handled by a separate job with appropriate permissions. - `add-reviewer:` - Add reviewers to pull requests ```yaml safe-outputs: