From 22bb54c7c39eb329e69fcd83723b04a32a7eb90b Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 7 Jan 2026 20:31:23 +0000 Subject: [PATCH] Sync github-agentic-workflows.md with v0.35.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Update instructions file with latest documentation changes: - Change create-agent-task to create-agent-session terminology - Add close-older-discussions field to create-discussion safe-output - Add deprecation notice for create-agent-task 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 --- .github/aw/github-agentic-workflows.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.github/aw/github-agentic-workflows.md b/.github/aw/github-agentic-workflows.md index 3b3b292db4..c193a97290 100644 --- a/.github/aw/github-agentic-workflows.md +++ b/.github/aw/github-agentic-workflows.md @@ -359,10 +359,13 @@ The YAML frontmatter supports these fields: title-prefix: "[ai] " # Optional: prefix for discussion titles category: "General" # Optional: discussion category name, slug, or ID (defaults to first category if not specified) max: 3 # Optional: maximum number of discussions (default: 1) + close-older-discussions: true # Optional: close older discussions with same prefix/labels (default: false) target-repo: "owner/repo" # Optional: cross-repository ``` The `category` field is optional and can be specified by name (e.g., "General"), slug (e.g., "general"), or ID (e.g., "DIC_kwDOGFsHUM4BsUn3"). If not specified, discussions will be created in the first available category. Category resolution tries ID first, then name, then slug. + Set `close-older-discussions: true` to automatically close older discussions matching the same title prefix or labels. Up to 10 older discussions are closed as "OUTDATED" with a comment linking to the new discussion. Requires `title-prefix` or `labels` to identify matching discussions. + When using `safe-outputs.create-discussion`, the main job does **not** need `discussions: write` permission since discussion creation is handled by a separate job with appropriate permissions. - `close-discussion:` - Close discussions with comment and resolution ```yaml @@ -557,14 +560,14 @@ The YAML frontmatter supports these fields: max: 50 # Optional: max findings (default: unlimited) ``` Severity levels: error, warning, info, note. - - `create-agent-task:` - Create GitHub Copilot agent tasks + - `create-agent-session:` - Create GitHub Copilot agent sessions ```yaml safe-outputs: - create-agent-task: + create-agent-session: base: main # Optional: base branch (defaults to current) target-repo: "owner/repo" # Optional: cross-repository ``` - Requires PAT as `COPILOT_GITHUB_TOKEN`. + Requires PAT as `COPILOT_GITHUB_TOKEN`. Note: `create-agent-task` is deprecated (use `create-agent-session`). - `assign-to-agent:` - Assign Copilot agents to issues ```yaml safe-outputs: