From 417d47b7579709e35c1110ff24fe4d2db1394f5b Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 21 Feb 2026 02:17:52 +0000 Subject: [PATCH 1/2] Initial plan From 4a3b65620557049fac6687fa198b61fd4a86115c Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 21 Feb 2026 02:27:00 +0000 Subject: [PATCH 2/2] fix: normalize report formatting for pr-triage-agent, ci-doctor, contribution-check, draft-pr-cleanup workflows Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/ci-doctor.md | 30 ++++++++++------ .github/workflows/contribution-check.md | 9 ++++- .github/workflows/draft-pr-cleanup.md | 22 ++++++++---- .github/workflows/pr-triage-agent.md | 46 ++++++++++++++++--------- 4 files changed, 74 insertions(+), 33 deletions(-) diff --git a/.github/workflows/ci-doctor.md b/.github/workflows/ci-doctor.md index e704984dfdf..1f16a59a27a 100644 --- a/.github/workflows/ci-doctor.md +++ b/.github/workflows/ci-doctor.md @@ -170,39 +170,49 @@ You are the CI Failure Doctor, an expert investigative agent that analyzes faile ### Investigation Issue Template +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. + When creating an investigation issue, use this structure: ```markdown -# ๐Ÿฅ CI Failure Investigation - Run #${{ github.event.workflow_run.run_number }} +### CI Failure Investigation - Run #${{ github.event.workflow_run.run_number }} -## Summary +### Summary [Brief description of the failure] -## Failure Details +### Failure Details - **Run**: [${{ github.event.workflow_run.id }}](${{ github.event.workflow_run.html_url }}) - **Commit**: ${{ github.event.workflow_run.head_sha }} - **Trigger**: ${{ github.event.workflow_run.event }} -## Root Cause Analysis +### Root Cause Analysis [Detailed analysis of what went wrong] -## Failed Jobs and Errors +### Failed Jobs and Errors [List of failed jobs with key error messages] -## Investigation Findings +
+Investigation Findings + [Deep analysis results] -## Recommended Actions +
+ +### Recommended Actions - [ ] [Specific actionable steps] -## Prevention Strategies +### Prevention Strategies [How to prevent similar failures] -## AI Team Self-Improvement +### AI Team Self-Improvement [Short set of additional prompting instructions to copy-and-paste into instructions.md for a AI coding agents to help prevent this type of failure in future] -## Historical Context +
+Historical Context + [Similar past failures and patterns] + +
``` ## Important Guidelines diff --git a/.github/workflows/contribution-check.md b/.github/workflows/contribution-check.md index d7984470fe7..bfab8d7d5a8 100644 --- a/.github/workflows/contribution-check.md +++ b/.github/workflows/contribution-check.md @@ -99,6 +99,8 @@ Follow the **report layout rules** below โ€” they apply to every report this wor Apply these principles to make the report scannable, warm, and actionable: +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. + 1. **Lead with the takeaway.** Open with a single-sentence human-readable summary that tells the maintainer what happened and what needs attention. No jargon, no counts-only headers. Example: *"We looked at 10 new PRs โ€” 6 look great, 3 need a closer look, and 1 doesn't fit the project guidelines."* 2. **Group by action, not by data.** Organize results into clear groups that answer "what should I do?" rather than listing raw rows. Use these groups (omit any group with zero items): @@ -119,7 +121,7 @@ Apply these principles to make the report scannable, warm, and actionable: ### Example Report ```markdown -## Contribution Check โ€” {date} +### Contribution Check โ€” {date} We looked at 4 new PRs โ€” 1 looks great, 2 need a closer look, and 1 doesn't fit the contribution guidelines. @@ -144,10 +146,15 @@ We looked at 4 new PRs โ€” 1 looks great, 2 need a closer look, and 1 doesn't fi ### Off-guidelines ๐Ÿ”ด +
+Per-PR Details + | PR | Title | Author | Lines | Quality | |----|-------|--------|------:|---------| | #4519 | Add unrelated marketing page | @dave | 42 | spam | +
+ --- Evaluated: 4 ยท Skipped: 10 diff --git a/.github/workflows/draft-pr-cleanup.md b/.github/workflows/draft-pr-cleanup.md index 88fa53e0897..fd556580e63 100644 --- a/.github/workflows/draft-pr-cleanup.md +++ b/.github/workflows/draft-pr-cleanup.md @@ -155,32 +155,42 @@ For each PR classified as "Ready to Close": ### Step 6: Generate Summary Report +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. + Create a summary of actions taken: ```markdown -## ๐Ÿงน Draft PR Cleanup Summary +### ๐Ÿงน Draft PR Cleanup Summary **Run Date**: -### Statistics +#### Statistics - **Total Draft PRs**: - **Exempt from Cleanup**: (keep-draft, blocked, or awaiting-review) - **Active (< 10 days)**: - **Warned (10-13 days)**: - **Closed (14+ days)**: -### Actions Taken +#### Actions Taken - **New Warnings Added**: - **PRs Closed**: - **PRs Skipped (exempt)**: -### PRs Warned This Run +
+PRs Warned This Run + -### PRs Closed This Run +
+ +
+PRs Closed This Run + -### Next Steps +
+ +#### Next Steps - Draft PRs currently in warning phase will be reviewed again tomorrow - Authors can prevent closure by adding activity or the `keep-draft` label - Closed PRs can be reopened if work continues diff --git a/.github/workflows/pr-triage-agent.md b/.github/workflows/pr-triage-agent.md index 023d96992d8..62a3b36ac34 100644 --- a/.github/workflows/pr-triage-agent.md +++ b/.github/workflows/pr-triage-agent.md @@ -251,7 +251,7 @@ For each PR, add the following labels: For each triaged PR, add a comment with the triage results: ```markdown -## ๐Ÿ” PR Triage Results +### ๐Ÿ” PR Triage Results **Category:** {category} | **Risk:** {risk} | **Priority:** {priority_score}/100 @@ -274,12 +274,14 @@ For each triaged PR, add a comment with the triage results: Create a comprehensive triage report as a GitHub Issue: +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. + **Report Structure:** ```markdown -# PR Triage Report - {date} +### PR Triage Report - {date} -## Executive Summary +### Executive Summary - **Total PRs Triaged:** {count} - **New PRs:** {new_count} @@ -289,9 +291,11 @@ Create a comprehensive triage report as a GitHub Issue: - **Batches Identified:** {batch_count} - **Close Candidates:** {close_count} -## Triage Statistics +### Triage Statistics + +
+By Category -### By Category - Bug: {bug_count} - Feature: {feature_count} - Docs: {docs_count} @@ -300,52 +304,62 @@ Create a comprehensive triage report as a GitHub Issue: - Refactor: {refactor_count} - Chore: {chore_count} -### By Risk Level +
+ +
+By Risk Level + - High Risk: {high_risk_count} - Medium Risk: {medium_risk_count} - Low Risk: {low_risk_count} -### By Priority +
+ +
+By Priority + - High Priority (70-100): {high_priority_count} - Medium Priority (40-69): {medium_priority_count} - Low Priority (0-39): {low_priority_count} -### By Recommended Action +
+ +#### By Recommended Action - Auto-merge: {auto_merge_count} - Fast-track: {fast_track_count} - Batch Review: {batch_review_count} - Defer: {defer_count} - Close: {close_count} -## ๐Ÿš€ Top Priority PRs (Top 10) +### ๐Ÿš€ Top Priority PRs (Top 10) {list_top_10_prs_with_scores_and_links} -## โœ… Auto-merge Candidates +### โœ… Auto-merge Candidates {list_auto_merge_prs} -## โšก Fast-track Review Needed +### โšก Fast-track Review Needed {list_fast_track_prs} -## ๐Ÿ“ฆ Batch Processing Opportunities +### ๐Ÿ“ฆ Batch Processing Opportunities {list_batches_with_pr_numbers} -## ๐Ÿ—‘๏ธ Close Candidates +### ๐Ÿ—‘๏ธ Close Candidates {list_close_candidate_prs_with_reasons} -## ๐Ÿ“Š Agent Performance Summary +### ๐Ÿ“Š Agent Performance Summary {summary_of_prs_by_agent_with_quality_scores} -## ๐Ÿ”„ Trends +### ๐Ÿ”„ Trends {compare_to_previous_runs_if_available} -## Next Steps +### Next Steps 1. Review auto-merge candidates for immediate merge 2. Fast-track high-priority PRs for urgent review