From a995d3c992af77bdee0a50f2cb1d60dc7a419246 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 12:35:41 +0000 Subject: [PATCH 1/2] Initial plan From 4f2a379b60ef647c3af43569614a66ae48fb557c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sun, 22 Feb 2026 12:52:19 +0000 Subject: [PATCH 2/2] Normalize report formatting for step-name-alignment and bot-detection workflows Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/bot-detection.md | 2 ++ .github/workflows/step-name-alignment.md | 4 +++- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/bot-detection.md b/.github/workflows/bot-detection.md index ca3f9d7b0c..a9fe823d6e 100644 --- a/.github/workflows/bot-detection.md +++ b/.github/workflows/bot-detection.md @@ -866,6 +866,8 @@ Maintain a **single** open triage issue with the exact title: ## Report Format (Issue Body) +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. + Produce a concise, evidence-driven report: - **Window**: last 6 hours (include timestamps) diff --git a/.github/workflows/step-name-alignment.md b/.github/workflows/step-name-alignment.md index b537f082b7..fb6af4ff41 100644 --- a/.github/workflows/step-name-alignment.md +++ b/.github/workflows/step-name-alignment.md @@ -248,9 +248,11 @@ When you identify problems worth addressing, create issues using safe-outputs. [step-names] Align step names in with glossary/consistency ``` +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. + **Issue Description Template:** ```markdown -## Step Name Alignment Issues +### Step Name Alignment Issues Found in: `.github/workflows/.lock.yml`