From dc175419b7953bab59598978f4f98b50e904d35c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 27 Feb 2026 04:27:06 +0000 Subject: [PATCH 1/3] Initial plan From 95cafd22cfac289e36c6134b93d0c5e7fe35cb51 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 27 Feb 2026 04:32:24 +0000 Subject: [PATCH 2/3] Update report.md to recommend disabling mentions and escaping GitHub references Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/aw/report.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/.github/aw/report.md b/.github/aw/report.md index fff1e5e336a..7df567ffedf 100644 --- a/.github/aw/report.md +++ b/.github/aw/report.md @@ -107,3 +107,26 @@ Reports should: - Format run IDs as links: `[§12345](https://github.com/owner/repo/actions/runs/12345)` - Include up to 3 most relevant run URLs at the end under `**References:**` - Do NOT add footer attribution — the system appends it automatically + +## Avoiding Mentions and Backlinks + +Reports are often posted on a schedule and reference many issues, PRs, or users. Unescaped references create noise: `@username` sends a notification, and `#123` creates a cross-reference backlink on that issue or PR. + +### Disable mentions + +**Never use bare `@mentions` in reports.** Mentioning a user or team by name will send a notification even if the report is just summarizing activity. + +- ❌ `@alice reviewed this PR` +- ✅ `alice reviewed this PR` (drop the `@`) +- ✅ `` `@alice` `` (wrap in backticks to render as code — no notification sent) + +### Escape GitHub automatic references + +GitHub automatically converts short references such as `#123`, `GH-123`, `owner/repo#123`, and bare commit SHAs into links and creates a backlink on the referenced item. To suppress this in reports, escape or reformat the reference: + +- ❌ `#123` — creates a backlink on issue/PR 123 +- ✅ `[#123](URL)` — renders as a link but **does not** create a backlink +- ✅ `` `#123` `` — renders as inline code, no backlink created +- ✅ `\#123` — escapes the `#`, renders literally, no backlink created + +Apply the same treatment to commit SHAs and cross-repo references (e.g. `owner/repo#123`) when they appear as plain text in a report body. From 82476372ce0f4d31fa301aabc40740b98ed3a8c0 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 27 Feb 2026 04:40:59 +0000 Subject: [PATCH 3/3] Update report.md to recommend safe-outputs built-in filtering for mentions and backlinks Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/aw/report.md | 33 +++++++++++++++++---------------- 1 file changed, 17 insertions(+), 16 deletions(-) diff --git a/.github/aw/report.md b/.github/aw/report.md index 7df567ffedf..6a36354a595 100644 --- a/.github/aw/report.md +++ b/.github/aw/report.md @@ -110,23 +110,24 @@ Reports should: ## Avoiding Mentions and Backlinks -Reports are often posted on a schedule and reference many issues, PRs, or users. Unescaped references create noise: `@username` sends a notification, and `#123` creates a cross-reference backlink on that issue or PR. +Reports often reference issues, PRs, or users. Without filtering, `@username` sends a notification and `#123` creates a cross-reference backlink on that issue or PR — adding noise every time the report runs. -### Disable mentions +Use the built-in safe-outputs filtering options to suppress this automatically: -**Never use bare `@mentions` in reports.** Mentioning a user or team by name will send a notification even if the report is just summarizing activity. +- **`mentions: false`** — escapes all `@mentions` in AI-generated output so no notifications are sent. +- **`allowed-github-references: []`** — escapes all `#123` / `owner/repo#123` references so no backlinks are created on referenced items. +- **`max-bot-mentions: 0`** — neutralizes bot-trigger phrases such as `fixes #123` or `closes #456` that would otherwise close referenced issues. -- ❌ `@alice reviewed this PR` -- ✅ `alice reviewed this PR` (drop the `@`) -- ✅ `` `@alice` `` (wrap in backticks to render as code — no notification sent) - -### Escape GitHub automatic references - -GitHub automatically converts short references such as `#123`, `GH-123`, `owner/repo#123`, and bare commit SHAs into links and creates a backlink on the referenced item. To suppress this in reports, escape or reformat the reference: - -- ❌ `#123` — creates a backlink on issue/PR 123 -- ✅ `[#123](URL)` — renders as a link but **does not** create a backlink -- ✅ `` `#123` `` — renders as inline code, no backlink created -- ✅ `\#123` — escapes the `#`, renders literally, no backlink created +```yaml +safe-outputs: + mentions: false + allowed-github-references: [] + max-bot-mentions: 0 + create-issue: + title-prefix: "Weekly Status:" + labels: [report] + close-older-issues: true + expires: 30 +``` -Apply the same treatment to commit SHAs and cross-repo references (e.g. `owner/repo#123`) when they appear as plain text in a report body. +These options apply globally to all safe-output types (issues, comments, discussions) and are the recommended way to keep reports from polluting unrelated items.