From c32c59dc194f642b634c69f38fa2066ecd409c23 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 21 Jan 2026 13:13:52 +0000 Subject: [PATCH 1/3] Initial plan From a68774702e1450f0fd2b811e8acb5b2e078a5bcf Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 21 Jan 2026 13:18:15 +0000 Subject: [PATCH 2/3] Initial plan: Add shared/reporting.md import to workflow-health-manager Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com> --- .github/workflows/stale-repo-identifier.lock.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/.github/workflows/stale-repo-identifier.lock.yml b/.github/workflows/stale-repo-identifier.lock.yml index d5591e9ae8e..a7a04973264 100644 --- a/.github/workflows/stale-repo-identifier.lock.yml +++ b/.github/workflows/stale-repo-identifier.lock.yml @@ -31,7 +31,6 @@ name: "Stale Repository Identifier" "on": schedule: - cron: "0 9 1 * *" - # Friendly format: every 12h (scattered) workflow_dispatch: inputs: organization: From 00facb6c6980a38fb6ffe83f5d89b4322f4ac40d Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 21 Jan 2026 13:24:53 +0000 Subject: [PATCH 3/3] Add shared/reporting.md import to workflow-health-manager Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com> --- .../workflow-health-manager.lock.yml | 76 +++++++++++++++++++ .github/workflows/workflow-health-manager.md | 2 + 2 files changed, 78 insertions(+) diff --git a/.github/workflows/workflow-health-manager.lock.yml b/.github/workflows/workflow-health-manager.lock.yml index 7447fa8480e..c6435ca7aa0 100644 --- a/.github/workflows/workflow-health-manager.lock.yml +++ b/.github/workflows/workflow-health-manager.lock.yml @@ -20,6 +20,10 @@ # For more information: https://github.com/githubnext/gh-aw/blob/main/.github/aw/github-agentic-workflows.md # # Meta-orchestrator for monitoring and managing health of all agentic workflows in the repository +# +# Resolved workflow manifest: +# Imports: +# - shared/reporting.md name: "Workflow Health Manager - Meta-Orchestrator" "on": @@ -685,6 +689,76 @@ jobs: PROMPT_EOF cat << 'PROMPT_EOF' >> "$GH_AW_PROMPT" + ## Report Structure Guidelines + + ### 1. Header Levels + **Use h3 (###) or lower for all headers in your issue report to maintain proper document hierarchy.** + + When creating GitHub issues or discussions: + - Use `###` (h3) for main sections (e.g., "### Test Summary") + - Use `####` (h4) for subsections (e.g., "#### Device-Specific Results") + - Never use `##` (h2) or `#` (h1) in reports - these are reserved for titles + + ### 2. Progressive Disclosure + **Wrap detailed test results in `
Section Name` tags to improve readability and reduce scrolling.** + + Use collapsible sections for: + - Verbose details (full test logs, raw data) + - Secondary information (minor warnings, extra context) + - Per-item breakdowns when there are many items + + Always keep critical information visible (summary, critical issues, key metrics). + + ### 3. Report Structure Pattern + + 1. **Overview**: 1-2 paragraphs summarizing key findings + 2. **Critical Information**: Show immediately (summary stats, critical issues) + 3. **Details**: Use `
Section Name` for expanded content + 4. **Context**: Add helpful metadata (workflow run, date, trigger) + + ### Design Principles (Airbnb-Inspired) + + Reports should: + - **Build trust through clarity**: Most important info immediately visible + - **Exceed expectations**: Add helpful context like trends, comparisons + - **Create delight**: Use progressive disclosure to reduce overwhelm + - **Maintain consistency**: Follow patterns across all reports + + ### Example Report Structure + + ```markdown + ### Summary + - Key metric 1: value + - Key metric 2: value + - Status: ✅/⚠️/❌ + + ### Critical Issues + [Always visible - these are important] + +
+ View Detailed Results + + [Comprehensive details, logs, traces] + +
+ +
+ View All Warnings + + [Minor issues and potential problems] + +
+ + ### Recommendations + [Actionable next steps - keep visible] + ``` + + ## Workflow Run References + + - Format run IDs as links: `[§12345](https://github.com/owner/repo/actions/runs/12345)` + - Include up to 3 most relevant run URLs at end under `**References:**` + - Do NOT add footer attribution (system adds automatically) + {{#runtime-import? .github/shared-instructions.md}} # Workflow Health Manager - Meta-Orchestrator @@ -1069,6 +1143,8 @@ jobs: **Systematic monitoring:** - Check ALL workflows, not just obviously failing ones - Track trends over time to catch degradation early + PROMPT_EOF + cat << 'PROMPT_EOF' >> "$GH_AW_PROMPT" - Be proactive about maintenance before workflows break - Consider workflow interdependencies when assessing health diff --git a/.github/workflows/workflow-health-manager.md b/.github/workflows/workflow-health-manager.md index c9b52b3ae2b..1cbd7a4e8fe 100644 --- a/.github/workflows/workflow-health-manager.md +++ b/.github/workflows/workflow-health-manager.md @@ -25,6 +25,8 @@ safe-outputs: update-issue: max: 5 timeout-minutes: 20 +imports: + - shared/reporting.md --- {{#runtime-import? .github/shared-instructions.md}}