From 80e0f56eb7f2a975cc3f4049df88615f9aeda6eb Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Sat, 4 Apr 2026 14:05:18 +0000 Subject: [PATCH] fix: remove bold formatting from details/summary sections in alerts (#24489) Agent-Logs-Url: https://github.com/github/gh-aw/sessions/f74d7586-5773-402a-9fe9-b5ab0707b70e Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/aw/create-agentic-workflow.md | 2 +- .../workflows_shared_reporting.md | 4 ++-- .github/aw/report.md | 8 ++++---- .github/workflows/agent-persona-explorer.md | 8 ++++---- .github/workflows/archie.md | 4 ++-- .github/workflows/auto-triage-issues.md | 6 +++--- .github/workflows/bot-detection.md | 2 +- .github/workflows/breaking-change-checker.md | 4 ++-- .github/workflows/ci-coach.md | 2 +- .github/workflows/ci-doctor.md | 18 +++++++++--------- .../workflows/claude-code-user-docs-review.md | 6 +++--- .github/workflows/cli-consistency-checker.md | 4 ++-- .github/workflows/cli-version-checker.md | 4 ++-- .github/workflows/constraint-solving-potd.md | 2 +- .github/workflows/contribution-check.md | 4 ++-- .github/workflows/copilot-cli-deep-research.md | 16 ++++++++-------- .github/workflows/copilot-pr-merged-report.md | 4 ++-- .github/workflows/daily-cli-performance.md | 8 ++++---- .github/workflows/daily-code-metrics.md | 2 +- .github/workflows/daily-compiler-quality.md | 6 +++--- .../workflows/daily-copilot-token-report.md | 14 +++++++------- .github/workflows/daily-doc-healer.md | 2 +- .github/workflows/daily-doc-updater.md | 2 +- .github/workflows/daily-file-diet.md | 8 ++++---- .github/workflows/daily-firewall-report.md | 4 ++-- .github/workflows/daily-function-namer.md | 2 +- .github/workflows/daily-integrity-analysis.md | 6 +++--- .github/workflows/daily-issues-report.md | 2 +- .../daily-mcp-concurrency-analysis.md | 4 ++-- .../daily-multi-device-docs-tester.md | 4 ++-- .github/workflows/daily-news.md | 4 ++-- .../workflows/daily-observability-report.md | 6 +++--- .github/workflows/daily-performance-summary.md | 2 +- .github/workflows/daily-regulatory.md | 2 +- .../workflows/daily-safe-output-optimizer.md | 4 ++-- .../daily-safe-outputs-conformance.md | 4 ++-- .github/workflows/daily-secrets-analysis.md | 6 +++--- .../workflows/daily-syntax-error-quality.md | 6 +++--- .../workflows/daily-team-evolution-insights.md | 8 ++++---- .../daily-testify-uber-super-expert.md | 4 ++-- .github/workflows/daily-workflow-updater.md | 2 +- .github/workflows/delight.md | 2 +- .github/workflows/dev-hawk.md | 4 ++-- .../workflows/developer-docs-consolidator.md | 2 +- .github/workflows/draft-pr-cleanup.md | 6 +++--- .../github-mcp-structural-analysis.md | 2 +- .github/workflows/issue-triage-agent.md | 2 +- .github/workflows/org-health-report.md | 4 ++-- .github/workflows/portfolio-analyst.md | 8 ++++---- .github/workflows/pr-nitpick-reviewer.md | 2 +- .github/workflows/pr-triage-agent.md | 8 ++++---- .../workflows/prompt-clustering-analysis.md | 2 +- .github/workflows/repo-audit-analyzer.md | 2 +- .../workflows/repository-quality-improver.md | 4 ++-- .github/workflows/scout.md | 4 ++-- .github/workflows/sergo.md | 2 +- .github/workflows/shared/reporting.md | 8 ++++---- .github/workflows/smoke-claude.lock.yml | 8 ++++---- .github/workflows/step-name-alignment.md | 2 +- .github/workflows/typist.md | 2 +- .../workflows/weekly-editors-health-check.md | 2 +- .../weekly-safe-outputs-spec-review.md | 2 +- .github/workflows/workflow-normalizer.md | 8 ++++---- .github/workflows/workflow-skill-extractor.md | 2 +- actions/setup/js/gateway_difc_filtered.cjs | 2 +- .../setup/js/gateway_difc_filtered.test.cjs | 12 ++++++------ .../js/generate_observability_summary.cjs | 2 +- .../js/generate_observability_summary.test.cjs | 2 +- actions/setup/js/handle_agent_failure.cjs | 4 ++-- actions/setup/js/handle_noop_message.test.cjs | 6 +++--- actions/setup/js/missing_info_formatter.cjs | 6 +++--- .../setup/js/missing_info_formatter.test.cjs | 6 +++--- actions/setup/js/parse_mcp_gateway_log.cjs | 12 ++++++------ .../setup/js/parse_mcp_gateway_log.test.cjs | 12 ++++++------ actions/setup/md/agent_failure_issue.md | 6 +++--- ...manifest_protection_push_failed_fallback.md | 2 +- .../manifest_protection_push_to_pr_fallback.md | 2 +- actions/setup/md/noop_runs_issue.md | 6 +++--- .../workflows_shared_reporting.md | 4 ++-- .../wasm_golden/fixtures/shared/reporting.md | 8 ++++---- scratchpad/gastown.md | 2 +- scratchpad/token-budget-guidelines.md | 4 ++-- 82 files changed, 198 insertions(+), 198 deletions(-) diff --git a/.github/aw/create-agentic-workflow.md b/.github/aw/create-agentic-workflow.md index a2144cbebcc..cb6d2384bfb 100644 --- a/.github/aw/create-agentic-workflow.md +++ b/.github/aw/create-agentic-workflow.md @@ -961,7 +961,7 @@ Include in the PR description: - Use GitHub-flavored markdown (GFM) for all output - **Headers**: Start at h3 (###) to maintain proper document hierarchy - **Checkboxes**: Use `- [ ]` for unchecked and `- [x]` for checked task items - - **Progressive Disclosure**: Use `
Bold Summary Text` to collapse long content + - **Progressive Disclosure**: Use `
Bold Summary Text` to collapse long content - **Workflow Run Links**: Format as `[ยง12345](https://github.com/owner/repo/actions/runs/12345)`. Do NOT add footer attribution (system adds automatically) - **Produce a single workflow file**: Always output exactly **one** workflow `.md` file as the primary deliverable. Do not create separate architecture documents, runbooks, usage guides, or any other documentation files alongside the workflow. - If documentation is needed, add a brief inline `## Usage` section within the same `.md` file. diff --git a/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md b/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md index c81c58d08b0..5e2936d214f 100644 --- a/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md +++ b/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md @@ -8,7 +8,7 @@ Structure your report with an overview followed by detailed content: 1. **Content Overview**: Start with 1-2 paragraphs that summarize the key findings, highlights, or main points of your report. This should give readers a quick understanding of what the report contains without needing to expand the details. -2. **Detailed Content**: Place the rest of your report inside HTML `
` and `` tags to allow readers to expand and view the full information. **IMPORTANT**: Always wrap the summary text in `` tags to make it bold. +2. **Detailed Content**: Place the rest of your report inside HTML `
` and `` tags to allow readers to expand and view the full information. **Example format:** @@ -18,7 +18,7 @@ Brief overview paragraph 1 introducing the report and its main findings. Optional overview paragraph 2 with additional context or highlights.
-Full Report Details +Full Report Details ## Detailed Analysis diff --git a/.github/aw/report.md b/.github/aw/report.md index 6a36354a595..4fa1fb2d1f1 100644 --- a/.github/aw/report.md +++ b/.github/aw/report.md @@ -49,7 +49,7 @@ When creating GitHub issues or discussions: ### Progressive Disclosure -**Wrap detailed content in `
Section Name` tags to improve readability and reduce scrolling.** +**Wrap detailed content in `
Section Name` tags to improve readability and reduce scrolling.** Use collapsible sections for: - Verbose details (full logs, raw data) @@ -62,7 +62,7 @@ Always keep critical information visible (summary, critical issues, key metrics) 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 +3. **Details**: Use `
Section Name` for expanded content 4. **Context**: Add helpful metadata (workflow run, date, trigger) ### Design Principles @@ -85,14 +85,14 @@ Reports should: [Always visible - these are important]
-View Detailed Results +View Detailed Results [Comprehensive details, logs, traces]
-View All Warnings +View All Warnings [Minor issues and potential problems] diff --git a/.github/workflows/agent-persona-explorer.md b/.github/workflows/agent-persona-explorer.md index a5fc7e5232b..dac4c5363d7 100644 --- a/.github/workflows/agent-persona-explorer.md +++ b/.github/workflows/agent-persona-explorer.md @@ -136,12 +136,12 @@ Follow these formatting guidelines when creating your persona analysis report: **Use h3 (###) or lower for all headers in persona analysis reports to maintain proper document hierarchy.** ### 2. Progressive Disclosure -**Wrap detailed examples and data tables in `
Section Name` tags to improve readability.** +**Wrap detailed examples and data tables in `
Section Name` tags to improve readability.** Example: ```markdown
-View Communication Examples +View Communication Examples [Detailed examples of agent outputs, writing style samples, tone analysis] @@ -165,14 +165,14 @@ Example: 3. [Security practices observed]
-View High Quality Responses (Top 2-3) +View High Quality Responses (Top 2-3) - [Scenario that worked well and why - keep brief]
-View Areas for Improvement (Top 2-3) +View Areas for Improvement (Top 2-3) - [Specific issues found - be direct] - [Suggestions for enhancement - actionable] diff --git a/.github/workflows/archie.md b/.github/workflows/archie.md index a0bb6601daa..fc6349ef537 100644 --- a/.github/workflows/archie.md +++ b/.github/workflows/archie.md @@ -151,7 +151,7 @@ Create a well-formatted comment containing your diagrams: **Comment Formatting**: Use h3 (`###`) or lower for all headers in your comment to maintain proper document hierarchy. The comment has no implicit title, so start section headers at h3. -If generating multiple diagrams, wrap diagrams 2 and 3 in `
View Additional Diagrams` tags to reduce scrolling. +If generating multiple diagrams, wrap diagrams 2 and 3 in `
View Additional Diagrams` tags to reduce scrolling. ### Comment Structure @@ -169,7 +169,7 @@ If generating multiple diagrams, wrap diagrams 2 and 3 in `
\```
-View Additional Diagrams +View Additional Diagrams #### [Diagram 2 Title] (if applicable) diff --git a/.github/workflows/auto-triage-issues.md b/.github/workflows/auto-triage-issues.md index b6df254bfb9..abaabb7bb0c 100644 --- a/.github/workflows/auto-triage-issues.md +++ b/.github/workflows/auto-triage-issues.md @@ -182,7 +182,7 @@ For the triggering issue (on issue events), you can omit `item_number`: When running on schedule, create a discussion report following these formatting guidelines: -**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 Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>10 items) in `
Section Name` tags to improve readability. ```markdown ### ๐Ÿท๏ธ Auto-Triage Report Summary @@ -206,7 +206,7 @@ When running on schedule, create a discussion report following these formatting | #125 | needs-triage | Low | Ambiguous description requiring human review |
-View Detailed Classification Analysis +View Detailed Classification Analysis #### Detailed Breakdown @@ -233,7 +233,7 @@ When running on schedule, create a discussion report following these formatting ### Label Distribution
-View Label Statistics +View Label Statistics - **bug**: X issues (Y% of processed) - **enhancement**: X issues (Y% of processed) diff --git a/.github/workflows/bot-detection.md b/.github/workflows/bot-detection.md index d64caefda6b..15a19637624 100644 --- a/.github/workflows/bot-detection.md +++ b/.github/workflows/bot-detection.md @@ -866,7 +866,7 @@ 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. +**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: diff --git a/.github/workflows/breaking-change-checker.md b/.github/workflows/breaking-change-checker.md index fbaaf114322..72ffc14f529 100644 --- a/.github/workflows/breaking-change-checker.md +++ b/.github/workflows/breaking-change-checker.md @@ -174,7 +174,7 @@ Create an issue with the following structure: | [sha] | [file path] | [category] | [description] | [user impact] |
-Full Code Diff Analysis +Full Code Diff Analysis #### Detailed Commit Analysis @@ -187,7 +187,7 @@ Create an issue with the following structure:
-All Commits Analyzed +All Commits Analyzed [Complete list of commits that were analyzed with their details] diff --git a/.github/workflows/ci-coach.md b/.github/workflows/ci-coach.md index 2226df402d8..3f24a3def26 100644 --- a/.github/workflows/ci-coach.md +++ b/.github/workflows/ci-coach.md @@ -181,7 +181,7 @@ If no improvements are found or changes are too risky: **Rationale**: Current integration tests wait unnecessarily for unit tests to complete. Integration tests don't use unit test outputs, so they can run in parallel. Splitting unit tests by package and rebalancing integration matrix reduces the critical path by 52%.
-View Detailed Test Structure Comparison +View Detailed Test Structure Comparison **Current Test Structure:** ```yaml diff --git a/.github/workflows/ci-doctor.md b/.github/workflows/ci-doctor.md index ee03d89fed6..b89f955dd0e 100644 --- a/.github/workflows/ci-doctor.md +++ b/.github/workflows/ci-doctor.md @@ -258,7 +258,7 @@ Check run data was fetched before this session:
-Detailed Analysis +Detailed Analysis @@ -271,7 +271,7 @@ Check run data was fetched before this session:
-Analysis Steps +Analysis Steps @@ -280,7 +280,7 @@ Check run data was fetched before this session: **IMPORTANT**: You **MUST** always end by calling `add_comment` (to post your diagnosis on the PR) or `noop` (if all checks are passing). Never finish without calling one of these. -**IMPORTANT**: Your comment **MUST** always include an **Analysis Steps** section (using `
Analysis Steps`) that summarizes what you did to reach your conclusions โ€” which tools you called, which logs you read, and what patterns you found. This gives readers progressive disclosure: a quick summary up front, with the full investigation trail available on demand. +**IMPORTANT**: Your comment **MUST** always include an **Analysis Steps** section (using `
Analysis Steps`) that summarizes what you did to reach your conclusions โ€” which tools you called, which logs you read, and what patterns you found. This gives readers progressive disclosure: a quick summary up front, with the full investigation trail available on demand. {{/if}} {{#if github.event.workflow_run.id}} @@ -406,7 +406,7 @@ Logs and artifacts have been pre-downloaded before this session started: - **Prevention Strategies**: How to avoid similar failures - **AI Team Self-Improvement**: Give a short set of additional prompting instructions to copy-and-paste into instructions.md for AI coding agents to help prevent this type of failure in future - **Historical Context**: Similar past failures and their resolutions - - **Analysis Steps**: A summary of every step you took to reach your conclusions (phases completed, tools called, files read, patterns matched) โ€” wrapped in a `
Analysis Steps` block for progressive disclosure + - **Analysis Steps**: A summary of every step you took to reach your conclusions (phases completed, tools called, files read, patterns matched) โ€” wrapped in a `
Analysis Steps` block for progressive disclosure 2. **Actionable Deliverables**: - Create an issue with investigation results (if warranted) @@ -418,7 +418,7 @@ Logs and artifacts have been pre-downloaded before this session started: ### 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. +**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: @@ -440,7 +440,7 @@ When creating an investigation issue, use this structure: [List of failed jobs with key error messages]
-Investigation Findings +Investigation Findings [Deep analysis results] @@ -456,14 +456,14 @@ When creating an investigation issue, use this structure: [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]
-Analysis Steps +Analysis Steps [Summary of the steps taken to investigate this failure: phases completed, tools called, files read, patterns matched] @@ -479,7 +479,7 @@ When creating an investigation issue, use this structure: - **Pattern Building**: Contribute to the knowledge base for future investigations - **Resource Efficient**: Use caching to avoid re-downloading large logs - **Security Conscious**: Never execute untrusted code from logs or external sources -- **Always Show Your Work**: Every report **must** include a collapsible `
Analysis Steps` section summarising the steps taken to reach your conclusions. This delights readers with progressive disclosure โ€” a quick overview first, full investigation trail on demand. +- **Always Show Your Work**: Every report **must** include a collapsible `
Analysis Steps` section summarising the steps taken to reach your conclusions. This delights readers with progressive disclosure โ€” a quick overview first, full investigation trail on demand. ## โš ๏ธ Mandatory Output Requirement diff --git a/.github/workflows/claude-code-user-docs-review.md b/.github/workflows/claude-code-user-docs-review.md index 3cbed50f7a1..59a1e977c56 100644 --- a/.github/workflows/claude-code-user-docs-review.md +++ b/.github/workflows/claude-code-user-docs-review.md @@ -283,7 +283,7 @@ I reviewed this documentation as a developer who: ### ๐Ÿšซ Critical Blockers (Score: X/10)
-Blocker 1: [Title] +Blocker 1: [Title] **Impact:** Cannot proceed with adoption @@ -302,7 +302,7 @@ I reviewed this documentation as a developer who: ### โš ๏ธ Major Obstacles (Score: X/10)
-Obstacle 1: [Title] +Obstacle 1: [Title] **Impact:** Significant friction in getting started @@ -469,7 +469,7 @@ Engine: custom - [X] workflows found ## Appendix: Files Reviewed
-Complete List of Documentation Files Analyzed +Complete List of Documentation Files Analyzed - `README.md` - `docs/src/content/docs/setup/quick-start.md` diff --git a/.github/workflows/cli-consistency-checker.md b/.github/workflows/cli-consistency-checker.md index c8a34e9e2f1..befaafcfe58 100644 --- a/.github/workflows/cli-consistency-checker.md +++ b/.github/workflows/cli-consistency-checker.md @@ -160,7 +160,7 @@ When issues are found, create a **single consolidated issue** that includes: - Suggested fix if applicable - Priority level: `high` (breaks functionality), `medium` (confusing/misleading), `low` (minor inconsistency) -**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>5 findings) in `
Section Name` tags to improve readability. The issue title serves as h1, so start section headers at h3. +**Report Formatting**: Use h3 (###) or lower for all headers in the report. Wrap long sections (>5 findings) in `
Section Name` tags to improve readability. The issue title serves as h1, so start section headers at h3. ### Issue Format @@ -197,7 +197,7 @@ Automated CLI consistency inspection found **X inconsistencies** in command help - [List areas with issues]
-Detailed Findings +Detailed Findings #### 1. [Issue Title] diff --git a/.github/workflows/cli-version-checker.md b/.github/workflows/cli-version-checker.md index 9120dd02048..bd8b7d1da73 100644 --- a/.github/workflows/cli-version-checker.md +++ b/.github/workflows/cli-version-checker.md @@ -206,7 +206,7 @@ Legacy template reference (adapt to use Report Structure Pattern above): - [New feature 2]
-View Full Changelog +View Full Changelog ### Release Highlights (from GitHub) [Include key highlights from GitHub release notes if available] @@ -232,7 +232,7 @@ Legacy template reference (adapt to use Report Structure Pattern above):
-View Migration Guide +View Migration Guide [Step-by-step update instructions, code changes needed if any] diff --git a/.github/workflows/constraint-solving-potd.md b/.github/workflows/constraint-solving-potd.md index 41af9d795b5..97f9890abad 100644 --- a/.github/workflows/constraint-solving-potd.md +++ b/.github/workflows/constraint-solving-potd.md @@ -74,7 +74,7 @@ Compare **at least two** ways to model this problem. For each approach: - Note trade-offs (expressiveness, propagation strength, scalability)
-Example Model (Pseudo-code) +Example Model (Pseudo-code) Provide a short, readable pseudo-code or MiniZinc/OPL/OR-Tools snippet showing one model. Keep it under 30 lines. diff --git a/.github/workflows/contribution-check.md b/.github/workflows/contribution-check.md index 708bee21c68..33c0931988c 100644 --- a/.github/workflows/contribution-check.md +++ b/.github/workflows/contribution-check.md @@ -102,7 +102,7 @@ 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. +**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."* @@ -150,7 +150,7 @@ We looked at 4 new PRs โ€” 1 looks great, 2 need a closer look, and 1 doesn't fi ### Off-guidelines ๐Ÿ”ด
-Per-PR Details +Per-PR Details | PR | Title | Author | Lines | Quality | |----|-------|--------|------:|---------| diff --git a/.github/workflows/copilot-cli-deep-research.md b/.github/workflows/copilot-cli-deep-research.md index b4403eabdc6..c7cee1bdfa7 100644 --- a/.github/workflows/copilot-cli-deep-research.md +++ b/.github/workflows/copilot-cli-deep-research.md @@ -244,7 +244,7 @@ Create a GitHub discussion with your comprehensive findings: ## 1๏ธโƒฃ Current State Analysis
-View Copilot CLI Capabilities Inventory +View Copilot CLI Capabilities Inventory ### Copilot CLI Capabilities Inventory - **Version Information**: [Current version used] @@ -254,7 +254,7 @@ Create a GitHub discussion with your comprehensive findings:
-View Usage Statistics +View Usage Statistics ### Usage Statistics - **Total Workflows**: [count] @@ -281,7 +281,7 @@ Create a GitHub discussion with your comprehensive findings: ## 3๏ธโƒฃ Missed Opportunities
-View High Priority Opportunities +View High Priority Opportunities ### ๐Ÿ”ด High Priority @@ -300,7 +300,7 @@ Create a GitHub discussion with your comprehensive findings:
-View Medium Priority Opportunities +View Medium Priority Opportunities ### ๐ŸŸก Medium Priority @@ -309,7 +309,7 @@ Create a GitHub discussion with your comprehensive findings:
-View Low Priority Opportunities +View Low Priority Opportunities ### ๐ŸŸข Low Priority @@ -322,7 +322,7 @@ Create a GitHub discussion with your comprehensive findings: ## 4๏ธโƒฃ Specific Workflow Recommendations
-View Workflow-Specific Recommendations +View Workflow-Specific Recommendations ### Workflow: `example-workflow.md` - **Current State**: [brief description] @@ -338,7 +338,7 @@ Create a GitHub discussion with your comprehensive findings: ## 5๏ธโƒฃ Trends & Insights
-View Historical Trends +View Historical Trends [If previous research exists in repo-memory] - **Changes Since Last Analysis**: [what's improved or changed] @@ -379,7 +379,7 @@ Based on this research, here are recommended best practices: ---
-View Supporting Evidence & Methodology +View Supporting Evidence & Methodology ## ๐Ÿ“š References diff --git a/.github/workflows/copilot-pr-merged-report.md b/.github/workflows/copilot-pr-merged-report.md index 6c3fcd634a3..2ab04018f8c 100644 --- a/.github/workflows/copilot-pr-merged-report.md +++ b/.github/workflows/copilot-pr-merged-report.md @@ -164,7 +164,7 @@ Create a concise report with the following structure: - Any PRs with exceptional metrics (very large, many test files, etc.)
-Merged Pull Requests +Merged Pull Requests | PR # | Title | Lines Added | Lines Deleted | Test Files | Merged At | |------|-------|-------------|---------------|------------|-----------| @@ -173,7 +173,7 @@ Create a concise report with the following structure:
-Code Generation Metrics +Code Generation Metrics - **Production Code**: [lines added - test lines added] lines - **Test Code**: [test lines added] lines diff --git a/.github/workflows/daily-cli-performance.md b/.github/workflows/daily-cli-performance.md index 3c572f38eaa..35b74e82373 100644 --- a/.github/workflows/daily-cli-performance.md +++ b/.github/workflows/daily-cli-performance.md @@ -407,7 +407,7 @@ If regressions are detected, open issues with detailed information. **Change**: [change_percent]% slower
-๐Ÿ“ˆ Detailed Performance Metrics +๐Ÿ“ˆ Detailed Performance Metrics #### Performance Comparison @@ -431,7 +431,7 @@ If regressions are detected, open issues with detailed information. 4. Compare with previous benchmark results: `benchstat`
-๐Ÿ“‹ Additional Context +๐Ÿ“‹ Additional Context - **Run ID**: ${{ github.run_id }} - **Date**: [date] @@ -558,7 +558,7 @@ def main(): # Detailed benchmark results (in details tag) f.write("
\n") - f.write("๐Ÿ“ˆ Detailed Benchmark Results\n\n") + f.write("๐Ÿ“ˆ Detailed Benchmark Results\n\n") for name, result in sorted(analysis['benchmarks'].items()): metrics = current['benchmarks'][name] @@ -585,7 +585,7 @@ def main(): # Historical comparisons (in details tag) f.write("
\n") - f.write("๐Ÿ“‰ Historical Comparisons\n\n") + f.write("๐Ÿ“‰ Historical Comparisons\n\n") f.write("### Trend Analysis\n\n") # Group by status diff --git a/.github/workflows/daily-code-metrics.md b/.github/workflows/daily-code-metrics.md index b40f2bbe915..b254aa3b414 100644 --- a/.github/workflows/daily-code-metrics.md +++ b/.github/workflows/daily-code-metrics.md @@ -307,7 +307,7 @@ Brief 2-3 paragraph executive summary highlighting key findings, quality score, [Trend analysis and significant changes]
-๐Ÿ“ˆ Detailed Metrics +๐Ÿ“ˆ Detailed Metrics ### Size Metrics diff --git a/.github/workflows/daily-compiler-quality.md b/.github/workflows/daily-compiler-quality.md index 014d6e0bd35..34894b9f321 100644 --- a/.github/workflows/daily-compiler-quality.md +++ b/.github/workflows/daily-compiler-quality.md @@ -333,7 +333,7 @@ Daily Compiler Code Quality Report - YYYY-MM-DD ### Files Analyzed Today
-๐Ÿ“ Detailed File Analysis +๐Ÿ“ Detailed File Analysis #### 1. `compiler_orchestrator.go` - Score: 82/100 โœ… @@ -442,7 +442,7 @@ Estimated Complexity Score: 7.2/10 ---
-๐Ÿ“ˆ Historical Trends +๐Ÿ“ˆ Historical Trends #### Progress Since Last Analysis @@ -510,7 +510,7 @@ Based on historical analysis, these files consistently score below 70: ---
-๐Ÿ’พ Cache Memory Summary +๐Ÿ’พ Cache Memory Summary **Cache Location**: `/tmp/gh-aw/cache-memory/compiler-quality/` diff --git a/.github/workflows/daily-copilot-token-report.md b/.github/workflows/daily-copilot-token-report.md index 8c30d53a775..ec46cf2c7bb 100644 --- a/.github/workflows/daily-copilot-token-report.md +++ b/.github/workflows/daily-copilot-token-report.md @@ -80,7 +80,7 @@ The discussion title serves as h1, so all content headers should start at h3: - Never use `##` (h2) or `#` (h1) in the report body ### 2. Progressive Disclosure -**Wrap detailed sections in `
Section Name` tags to improve readability and reduce scrolling.** +**Wrap detailed sections in `
Section Name` tags to improve readability and reduce scrolling.** Use collapsible sections for: - Per-workflow detailed statistics tables @@ -91,7 +91,7 @@ Use collapsible sections for: Example: ```markdown
-Per-Workflow Detailed Statistics +Per-Workflow Detailed Statistics | Workflow | Runs | Total Tokens | Avg Tokens | Total Cost | Avg Cost | |----------|------|--------------|------------|------------|----------| @@ -584,7 +584,7 @@ Daily cost trends show [analysis of cost patterns, efficiency, and notable chang | ... | ... | ... | ... | ... | ... | ... |
-Per-Workflow Detailed Statistics (All Workflows) +Per-Workflow Detailed Statistics (All Workflows) | Workflow | Total Tokens | Total Cost | Runs | Avg Tokens | Avg Cost | Avg Turns | Avg Duration | |----------|--------------|------------|------|------------|----------|-----------|--------------| @@ -608,7 +608,7 @@ The following workflows account for the majority of token consumption: - **Recommendation**: [Suggestion]
-Optimization Opportunities +Optimization Opportunities 1. **[Opportunity 1]**: [Description] - **Affected Workflows**: [list] @@ -623,7 +623,7 @@ The following workflows account for the majority of token consumption:
-Efficiency Trends +Efficiency Trends - **Token efficiency**: [Analysis of avg tokens per turn or per workflow] - **Cost efficiency**: [Analysis of cost trends and efficiency improvements] @@ -632,7 +632,7 @@ The following workflows account for the majority of token consumption:
-Historical Comparison +Historical Comparison | Metric | Last 7 Days | Previous 7 Days | Change | Last 30 Days | |--------|-------------|-----------------|--------|--------------| @@ -644,7 +644,7 @@ The following workflows account for the majority of token consumption:
-Methodology & Data Quality Notes +Methodology & Data Quality Notes #### Methodology - **Data Source**: GitHub Actions workflow run artifacts from last 30 days diff --git a/.github/workflows/daily-doc-healer.md b/.github/workflows/daily-doc-healer.md index c11c79fbe2d..426ef4908a9 100644 --- a/.github/workflows/daily-doc-healer.md +++ b/.github/workflows/daily-doc-healer.md @@ -176,7 +176,7 @@ This PR was automatically created by the Daily Documentation Healer workflow. [Explanation of why DDUw missed this]
-๐Ÿ’ก DDUw Improvement Suggestions +๐Ÿ’ก DDUw Improvement Suggestions ### DDUw Improvement Suggestions diff --git a/.github/workflows/daily-doc-updater.md b/.github/workflows/daily-doc-updater.md index 3108c4658fa..61f5d1cf35d 100644 --- a/.github/workflows/daily-doc-updater.md +++ b/.github/workflows/daily-doc-updater.md @@ -235,7 +235,7 @@ This PR updates the documentation based on features merged in the last 24 hours. - Feature 2 (from #PR_NUMBER)
-๐Ÿ“ Detailed Changes & References +๐Ÿ“ Detailed Changes & References ### Changes Made diff --git a/.github/workflows/daily-file-diet.md b/.github/workflows/daily-file-diet.md index c4591909eba..e1e77ee7df1 100644 --- a/.github/workflows/daily-file-diet.md +++ b/.github/workflows/daily-file-diet.md @@ -123,7 +123,7 @@ If refactoring is needed (file โ‰ฅ 800 lines), create an issue with this structu 1. **Header Levels**: Use h3 (###) or lower for all headers in your issue report to maintain proper document hierarchy. The issue title serves as h1, so start section headers at h3. -2. **Progressive Disclosure**: Wrap detailed file analysis, code snippets, and lengthy explanations in `
Section Name` tags to improve readability and reduce overwhelm. This keeps the most important information immediately visible while allowing readers to expand sections as needed. +2. **Progressive Disclosure**: Wrap detailed file analysis, code snippets, and lengthy explanations in `
Section Name` tags to improve readability and reduce overwhelm. This keeps the most important information immediately visible while allowing readers to expand sections as needed. 3. **Issue Structure**: Follow this pattern for optimal clarity: - **Brief summary** of the file size issue (always visible) @@ -148,7 +148,7 @@ The file `[FILE_PATH]` has grown to [LINE_COUNT] lines, making it difficult to m - **Complexity**: [Brief assessment from Serena analysis]
-Full File Analysis +Full File Analysis #### Detailed Breakdown @@ -193,7 +193,7 @@ Consider introducing interfaces to reduce coupling: - [Interface suggestions]
-Test Coverage Plan +Test Coverage Plan Add comprehensive tests for each new file: @@ -232,7 +232,7 @@ Add comprehensive tests for each new file: - [ ] Build succeeds (`make build`)
-Additional Context +Additional Context - **Repository Guidelines**: Follow patterns in `.github/agents/developer.instructions.agent.md` - **Code Organization**: Prefer many small files grouped by functionality diff --git a/.github/workflows/daily-firewall-report.md b/.github/workflows/daily-firewall-report.md index af5173996c1..3e0a804e575 100644 --- a/.github/workflows/daily-firewall-report.md +++ b/.github/workflows/daily-firewall-report.md @@ -433,7 +433,7 @@ Provide a brief analysis: ```markdown
-View Detailed Request Patterns by Workflow +View Detailed Request Patterns by Workflow For each workflow that had blocked domains, provide a detailed breakdown: @@ -458,7 +458,7 @@ For each workflow that had blocked domains, provide a detailed breakdown: ```markdown
-View Complete Blocked Domains List +View Complete Blocked Domains List An alphabetically sorted list of all unique blocked domains: diff --git a/.github/workflows/daily-function-namer.md b/.github/workflows/daily-function-namer.md index 73950818541..d8aea4b3e1b 100644 --- a/.github/workflows/daily-function-namer.md +++ b/.github/workflows/daily-function-namer.md @@ -276,7 +276,7 @@ that an agent will find the right function instead of reimplementing existing lo ---
-๐Ÿค– Agentic Implementation Plan +๐Ÿค– Agentic Implementation Plan ### Agentic Implementation Plan diff --git a/.github/workflows/daily-integrity-analysis.md b/.github/workflows/daily-integrity-analysis.md index 1a7d32b7c4c..c3789028e7e 100644 --- a/.github/workflows/daily-integrity-analysis.md +++ b/.github/workflows/daily-integrity-analysis.md @@ -445,7 +445,7 @@ In the last 7 days, **[N]** DIFC integrity-filtered events were detected across [Analysis of integrity vs. secrecy filtering and top tags]
-๐Ÿ“‹ Per-Workflow Breakdown +๐Ÿ“‹ Per-Workflow Breakdown | Workflow | Filtered Events | |----------|----------------| @@ -454,7 +454,7 @@ In the last 7 days, **[N]** DIFC integrity-filtered events were detected across
-๐Ÿ“‹ Per-Server Breakdown +๐Ÿ“‹ Per-Server Breakdown | MCP Server | Filtered Events | |------------|----------------| @@ -463,7 +463,7 @@ In the last 7 days, **[N]** DIFC integrity-filtered events were detected across
-๐Ÿ‘ค Per-User Breakdown +๐Ÿ‘ค Per-User Breakdown | Author Login | Filtered Events | |--------------|----------------| diff --git a/.github/workflows/daily-issues-report.md b/.github/workflows/daily-issues-report.md index 4405718254b..ff065c045e4 100644 --- a/.github/workflows/daily-issues-report.md +++ b/.github/workflows/daily-issues-report.md @@ -248,7 +248,7 @@ Create a new discussion with the comprehensive report. Brief 2-3 paragraph summary of key findings: total issues analyzed, main clusters identified, notable trends, and any concerns that need attention.
-๐Ÿ“Š Full Report Details +๐Ÿ“Š Full Report Details ### ๐Ÿ“ˆ Issue Activity Trends diff --git a/.github/workflows/daily-mcp-concurrency-analysis.md b/.github/workflows/daily-mcp-concurrency-analysis.md index d422ee24931..bb2493ccd83 100644 --- a/.github/workflows/daily-mcp-concurrency-analysis.md +++ b/.github/workflows/daily-mcp-concurrency-analysis.md @@ -312,7 +312,7 @@ Use the following template: 4. Result: [Data corruption / lost updates / incorrect behavior]
-Detailed Analysis +Detailed Analysis #### Root Cause @@ -353,7 +353,7 @@ Use the following template: 3. [Step 3]
-Alternative Solutions +Alternative Solutions **Option 1: [Alternative approach 1]** - Pros: [Benefits] diff --git a/.github/workflows/daily-multi-device-docs-tester.md b/.github/workflows/daily-multi-device-docs-tester.md index 616ec693607..ceb2c4aafda 100644 --- a/.github/workflows/daily-multi-device-docs-tester.md +++ b/.github/workflows/daily-multi-device-docs-tester.md @@ -187,14 +187,14 @@ Create a GitHub issue titled "๐Ÿ” Multi-Device Docs Testing Report - [Date]" wi [List critical issues that block functionality or major accessibility problems - keep visible]
-View All Warnings +View All Warnings [Minor issues and potential problems with device names and details]
-View Detailed Test Results by Device +View Detailed Test Results by Device #### Mobile Devices [Test results, screenshots, findings] diff --git a/.github/workflows/daily-news.md b/.github/workflows/daily-news.md index 28299b64ebc..384e7b4a6a4 100644 --- a/.github/workflows/daily-news.md +++ b/.github/workflows/daily-news.md @@ -418,7 +418,7 @@ Include the charts in your daily news discussion report with this structure: ### ๐Ÿ“ˆ Trend Analysis
-Issues & Pull Requests Activity +Issues & Pull Requests Activity ![Issues and PR Trends](URL_FROM_UPLOAD_ASSET_CHART_1) @@ -427,7 +427,7 @@ Include the charts in your daily news discussion report with this structure:
-Commit Activity & Contributors +Commit Activity & Contributors ![Commit Activity Trends](URL_FROM_UPLOAD_ASSET_CHART_2) diff --git a/.github/workflows/daily-observability-report.md b/.github/workflows/daily-observability-report.md index 44df8faf202..ce2e3a193eb 100644 --- a/.github/workflows/daily-observability-report.md +++ b/.github/workflows/daily-observability-report.md @@ -277,7 +277,7 @@ Follow the formatting guidelines above. Use the following structure: [Always visible. Summary table showing high-level coverage metrics.]
-๐Ÿ“‹ Detailed Run Analysis +๐Ÿ“‹ Detailed Run Analysis #### Firewall-Enabled Runs @@ -306,7 +306,7 @@ Follow the formatting guidelines above. Use the following structure:
-๐Ÿ” Telemetry Quality Analysis +๐Ÿ” Telemetry Quality Analysis #### Firewall Log Quality @@ -339,7 +339,7 @@ Follow the formatting guidelines above. Use the following structure: [Always visible. Actionable recommendations based on the analysis.]
-๐Ÿ“Š Historical Trends +๐Ÿ“Š Historical Trends [If historical data is available, show trends in observability coverage over time] diff --git a/.github/workflows/daily-performance-summary.md b/.github/workflows/daily-performance-summary.md index f4a839fd70a..802e283e27e 100644 --- a/.github/workflows/daily-performance-summary.md +++ b/.github/workflows/daily-performance-summary.md @@ -411,7 +411,7 @@ Create a new discussion with the comprehensive performance report. [Brief 2-3 sentence analysis of activity distribution across PRs, issues, and discussions]
-๐Ÿ“Š Detailed Benchmark Results +๐Ÿ“Š Detailed Benchmark Results #### ๐ŸŽฏ Resolution Metrics diff --git a/.github/workflows/daily-regulatory.md b/.github/workflows/daily-regulatory.md index 18245ce45eb..ddcfed84ece 100644 --- a/.github/workflows/daily-regulatory.md +++ b/.github/workflows/daily-regulatory.md @@ -266,7 +266,7 @@ Brief 2-3 paragraph executive summary highlighting: - Key findings and any critical issues
-๐Ÿ“‹ Full Regulatory Report +๐Ÿ“‹ Full Regulatory Report ### ๐Ÿ“Š Reports Reviewed diff --git a/.github/workflows/daily-safe-output-optimizer.md b/.github/workflows/daily-safe-output-optimizer.md index 61cdd892639..42136e506b0 100644 --- a/.github/workflows/daily-safe-output-optimizer.md +++ b/.github/workflows/daily-safe-output-optimizer.md @@ -226,7 +226,7 @@ Use the cache memory folder `/tmp/gh-aw/cache-memory/` to build persistent knowl Analysis of the last 24 hours of workflow runs identified **[N] errors** where agents incorrectly used the `[tool_name]` safe output tool. The workflow prompts appear correct, indicating the tool description needs improvement.
-๐Ÿ” Error Analysis Details +๐Ÿ” Error Analysis Details ### Error Analysis @@ -267,7 +267,7 @@ Analysis of the last 24 hours of workflow runs identified **[N] errors** where a ### Current Tool Description
-Current description from safe_outputs_tools.json +Current description from safe_outputs_tools.json ```json [Include relevant excerpt from pkg/workflow/js/safe_outputs_tools.json] diff --git a/.github/workflows/daily-safe-outputs-conformance.md b/.github/workflows/daily-safe-outputs-conformance.md index 634ae69e68e..446552d09f0 100644 --- a/.github/workflows/daily-safe-outputs-conformance.md +++ b/.github/workflows/daily-safe-outputs-conformance.md @@ -117,7 +117,7 @@ Example: `SEC-001: Agent job in workflow X has write permissions` - **Handlers**: [List handler files if applicable]
-๐Ÿ” Current vs Expected Behavior +๐Ÿ” Current vs Expected Behavior ### Current Behavior @@ -185,7 +185,7 @@ After processing all issues, provide a summary in the workflow output: **Script Exit Code**: [exit_code]
-๐Ÿ“Š Detailed Results & Actions +๐Ÿ“Š Detailed Results & Actions ### Results diff --git a/.github/workflows/daily-secrets-analysis.md b/.github/workflows/daily-secrets-analysis.md index 6d87edff436..b43ff7c02bb 100644 --- a/.github/workflows/daily-secrets-analysis.md +++ b/.github/workflows/daily-secrets-analysis.md @@ -234,7 +234,7 @@ Use the following template for the discussion post: 2. **Recommendation 2**: Action to take
-๐Ÿ”‘ Top 10 Secrets by Usage +๐Ÿ”‘ Top 10 Secrets by Usage | Rank | Secret Name | Occurrences | Type | |------|-------------|-------------|------| @@ -245,7 +245,7 @@ Use the following template for the discussion post:
-๐Ÿ“ˆ Trends +๐Ÿ“ˆ Trends [If historical data available, show changes from previous day] @@ -256,7 +256,7 @@ Use the following template for the discussion post:
-๐Ÿ“– Reference Documentation +๐Ÿ“– Reference Documentation For detailed information about secret usage patterns, see: - Specification: [`scratchpad/secrets-yml.md`](https://github.com/github/gh-aw/blob/main/scratchpad/secrets-yml.md) diff --git a/.github/workflows/daily-syntax-error-quality.md b/.github/workflows/daily-syntax-error-quality.md index 8e5ff198a98..117a381984a 100644 --- a/.github/workflows/daily-syntax-error-quality.md +++ b/.github/workflows/daily-syntax-error-quality.md @@ -386,7 +386,7 @@ Create a detailed evaluation for each test case: ### Test Case Results
-Test Case 1: Invalid YAML Syntax - Score: 82/100 โœ… +Test Case 1: Invalid YAML Syntax - Score: 82/100 โœ… #### Test Configuration @@ -442,14 +442,14 @@ Create a detailed evaluation for each test case:
-Test Case 2: Invalid Engine Name - Score: 68/100 โš ๏ธ +Test Case 2: Invalid Engine Name - Score: 68/100 โš ๏ธ [Similar detailed analysis...]
-Test Case 3: Conflicting Configuration - Score: 74/100 โœ… +Test Case 3: Conflicting Configuration - Score: 74/100 โœ… [Similar detailed analysis...] diff --git a/.github/workflows/daily-team-evolution-insights.md b/.github/workflows/daily-team-evolution-insights.md index 017a5baed0c..dfc138802d7 100644 --- a/.github/workflows/daily-team-evolution-insights.md +++ b/.github/workflows/daily-team-evolution-insights.md @@ -117,7 +117,7 @@ Always create a GitHub Discussion with your findings using this structure: - ๐Ÿ’ก **Innovation**: [New technologies, approaches, or experiments being explored]
-๐Ÿ“Š Detailed Activity Snapshot +๐Ÿ“Š Detailed Activity Snapshot ### Development Activity @@ -147,7 +147,7 @@ Always create a GitHub Discussion with your findings using this structure:
-๐Ÿ‘ฅ Team Dynamics Deep Dive +๐Ÿ‘ฅ Team Dynamics Deep Dive ### Active Contributors @@ -205,7 +205,7 @@ Always create a GitHub Discussion with your findings using this structure: [Based on current patterns, what might we expect to see developing? What opportunities are emerging? What should the team keep in mind?]
-๐Ÿ“š Complete Resource Links +๐Ÿ“š Complete Resource Links ### Pull Requests [Links to all relevant PRs with brief descriptions] @@ -234,7 +234,7 @@ Always create a GitHub Discussion with your findings using this structure: ```markdown
-Section Title +Section Title [Content goes here] diff --git a/.github/workflows/daily-testify-uber-super-expert.md b/.github/workflows/daily-testify-uber-super-expert.md index 0bde0c56ea7..0253e3220a4 100644 --- a/.github/workflows/daily-testify-uber-super-expert.md +++ b/.github/workflows/daily-testify-uber-super-expert.md @@ -202,7 +202,7 @@ The test file `[FILE_PATH]` has been selected for quality improvement by the Tes [List 2-3 things the test file does well]
-๐ŸŽฏ Areas for Improvement +๐ŸŽฏ Areas for Improvement ### Areas for Improvement ๐ŸŽฏ @@ -339,7 +339,7 @@ require.NoError(t, err, "setup should succeed without errors")
-๐Ÿ“‹ Implementation Guidelines +๐Ÿ“‹ Implementation Guidelines #### Priority Order 1. **High**: Add missing tests for critical functions diff --git a/.github/workflows/daily-workflow-updater.md b/.github/workflows/daily-workflow-updater.md index 93f8afde47c..282e140adcb 100644 --- a/.github/workflows/daily-workflow-updater.md +++ b/.github/workflows/daily-workflow-updater.md @@ -125,7 +125,7 @@ If `.github/aw/actions-lock.json` has changes: This PR updates GitHub Actions versions in `.github/aw/actions-lock.json` to their latest compatible releases.
-๐Ÿ“ฆ Actions Updated (full list) +๐Ÿ“ฆ Actions Updated (full list) ### Actions Updated diff --git a/.github/workflows/delight.md b/.github/workflows/delight.md index 4ed37b7603e..cea421f7272 100644 --- a/.github/workflows/delight.md +++ b/.github/workflows/delight.md @@ -255,7 +255,7 @@ For each selected item: ### Step 4: Create Improvement Report -**Report Formatting**: Use h3 (###) or lower for all headers in the report to maintain proper document hierarchy. Wrap long sections in `
Section Name` tags to improve readability. +**Report Formatting**: Use h3 (###) or lower for all headers in the report to maintain proper document hierarchy. Wrap long sections in `
Section Name` tags to improve readability. Create a focused analysis report: diff --git a/.github/workflows/dev-hawk.md b/.github/workflows/dev-hawk.md index de7003f20e6..deb0ee58099 100644 --- a/.github/workflows/dev-hawk.md +++ b/.github/workflows/dev-hawk.md @@ -161,7 +161,7 @@ Dev workflow completed successfully! ๐ŸŽ‰ - `path/to/another.ext` - [Another issue if applicable]
-๐Ÿ” Error Details +๐Ÿ” Error Details ``` [Key error messages from audit] @@ -193,7 +193,7 @@ If you prefer to fix this manually: [Summary of failure from audit]
-๐Ÿ” Key Errors +๐Ÿ” Key Errors [Error messages and patterns found] diff --git a/.github/workflows/developer-docs-consolidator.md b/.github/workflows/developer-docs-consolidator.md index 7af5a9244ea..a830ad8b5b3 100644 --- a/.github/workflows/developer-docs-consolidator.md +++ b/.github/workflows/developer-docs-consolidator.md @@ -385,7 +385,7 @@ Create a comprehensive report of what was done: Analyzed [N] markdown files in the specs directory, made [X] tone adjustments, added [Y] Mermaid diagrams, and consolidated content into `scratchpad/dev.md`.
-Full Consolidation Report +Full Consolidation Report ## Files Analyzed diff --git a/.github/workflows/draft-pr-cleanup.md b/.github/workflows/draft-pr-cleanup.md index c082ed93705..a8fe6d1ad2e 100644 --- a/.github/workflows/draft-pr-cleanup.md +++ b/.github/workflows/draft-pr-cleanup.md @@ -157,7 +157,7 @@ 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. +**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: @@ -179,14 +179,14 @@ Create a summary of actions taken: - **PRs Skipped (exempt)**:
-PRs Warned This Run +PRs Warned This Run
-PRs Closed This Run +PRs Closed This Run diff --git a/.github/workflows/github-mcp-structural-analysis.md b/.github/workflows/github-mcp-structural-analysis.md index a5a354a71e6..edf1c502626 100644 --- a/.github/workflows/github-mcp-structural-analysis.md +++ b/.github/workflows/github-mcp-structural-analysis.md @@ -245,7 +245,7 @@ Brief overview with key findings (tools analyzed, best/worst usefulness ratings, ```markdown
-Full Structural Analysis Report +Full Structural Analysis Report ## Executive Summary diff --git a/.github/workflows/issue-triage-agent.md b/.github/workflows/issue-triage-agent.md index b630936addf..a43f13a085f 100644 --- a/.github/workflows/issue-triage-agent.md +++ b/.github/workflows/issue-triage-agent.md @@ -38,7 +38,7 @@ Hi @{author}! I've categorized this issue as **{label_name}** based on the follo **Reasoning**: {brief_explanation_of_why_this_label}
-View Triage Details +View Triage Details #### Analysis - **Keywords detected**: {list_of_keywords_that_matched} diff --git a/.github/workflows/org-health-report.md b/.github/workflows/org-health-report.md index bfc056b7764..e70b0597419 100644 --- a/.github/workflows/org-health-report.md +++ b/.github/workflows/org-health-report.md @@ -386,7 +386,7 @@ Use the `create discussion` safe-output to publish the report: ...
-Top 10 Most Active Authors +Top 10 Most Active Authors | Author | Issues Opened | PRs Opened | Activity Score | |--------|---------------|------------|----------------| @@ -424,7 +424,7 @@ Use the `create discussion` safe-output to publish the report: [Analysis of the metrics and suggestions for where maintainers should focus their attention]
-Full Data and Methodology +Full Data and Methodology #### Data Collection diff --git a/.github/workflows/portfolio-analyst.md b/.github/workflows/portfolio-analyst.md index 6354be0f363..0bd0bc6cbfc 100644 --- a/.github/workflows/portfolio-analyst.md +++ b/.github/workflows/portfolio-analyst.md @@ -367,7 +367,7 @@ Top 3 workflows account for [X]% of total cost: **Total Potential Savings: $[X]/month ([Y]% reduction)**
-Strategy 1: Fix High-Failure Workflows - $[X]/month +Strategy 1: Fix High-Failure Workflows - $[X]/month List workflows with >30% failure rate, showing: - Workflow name and file @@ -378,7 +378,7 @@ List workflows with >30% failure rate, showing:
-Strategy 2: Reduce Over-Scheduling - $[Y]/month +Strategy 2: Reduce Over-Scheduling - $[Y]/month List over-scheduled workflows with: - Current frequency (runs/month) @@ -388,14 +388,14 @@ List over-scheduled workflows with:
-Strategy 3: Disable Failed Workflows - $[Z]/month +Strategy 3: Disable Failed Workflows - $[Z]/month List workflows with 100% failure rate or no successful runs.
-Strategy 4: Remove Unused Workflows - $[W]/month +Strategy 4: Remove Unused Workflows - $[W]/month List workflows with no runs in 60+ days. diff --git a/.github/workflows/pr-nitpick-reviewer.md b/.github/workflows/pr-nitpick-reviewer.md index d16db1090d9..f0a13e1bf5b 100644 --- a/.github/workflows/pr-nitpick-reviewer.md +++ b/.github/workflows/pr-nitpick-reviewer.md @@ -197,7 +197,7 @@ Create a comprehensive markdown report using the imported `reporting.md` format: Brief overview of the review findings and key patterns observed.
-Full Review Report +Full Review Report #### Pull Request Overview diff --git a/.github/workflows/pr-triage-agent.md b/.github/workflows/pr-triage-agent.md index 83c9c13d89a..fd4c7ba9b5c 100644 --- a/.github/workflows/pr-triage-agent.md +++ b/.github/workflows/pr-triage-agent.md @@ -277,7 +277,7 @@ 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 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:** @@ -297,7 +297,7 @@ Create a comprehensive triage report as a GitHub Issue: ### Triage Statistics
-By Category +By Category - Bug: {bug_count} - Feature: {feature_count} @@ -310,7 +310,7 @@ Create a comprehensive triage report as a GitHub Issue:
-By Risk Level +By Risk Level - High Risk: {high_risk_count} - Medium Risk: {medium_risk_count} @@ -319,7 +319,7 @@ Create a comprehensive triage report as a GitHub Issue:
-By Priority +By Priority - High Priority (70-100): {high_priority_count} - Medium Priority (40-69): {medium_priority_count} diff --git a/.github/workflows/prompt-clustering-analysis.md b/.github/workflows/prompt-clustering-analysis.md index fc32036d9ed..863a0d2fa9d 100644 --- a/.github/workflows/prompt-clustering-analysis.md +++ b/.github/workflows/prompt-clustering-analysis.md @@ -491,7 +491,7 @@ Create a comprehensive discussion report with: **Overall Success Rate**: [percentage]%
-Full Analysis Report +Full Analysis Report ### General Insights diff --git a/.github/workflows/repo-audit-analyzer.md b/.github/workflows/repo-audit-analyzer.md index 7fc0a1be5da..61b5583447d 100644 --- a/.github/workflows/repo-audit-analyzer.md +++ b/.github/workflows/repo-audit-analyzer.md @@ -408,7 +408,7 @@ Create a detailed analysis report with actionable recommendations: ## ๐Ÿ—๏ธ Repository Overview
-Project Details +Project Details ### Project Information - **Name**: [Name] diff --git a/.github/workflows/repository-quality-improver.md b/.github/workflows/repository-quality-improver.md index d58c9efbc6f..8118a650b66 100644 --- a/.github/workflows/repository-quality-improver.md +++ b/.github/workflows/repository-quality-improver.md @@ -306,7 +306,7 @@ Create a comprehensive report using the **reporting MCP** with the following str [2-3 paragraphs summarizing the analysis findings and key recommendations]
-Full Analysis Report +Full Analysis Report ### Focus Area: [AREA NAME] @@ -398,7 +398,7 @@ The following code regions and tasks should be processed by the Copilot coding a ## ๐Ÿ“Š Historical Context
-Previous Focus Areas +Previous Focus Areas | Date | Focus Area | Type | Custom | Key Outcomes | |------|------------|------|--------|--------------| diff --git a/.github/workflows/scout.md b/.github/workflows/scout.md index 34c3b7de47a..e0c7f3fa46d 100644 --- a/.github/workflows/scout.md +++ b/.github/workflows/scout.md @@ -135,7 +135,7 @@ Create a comprehensive research summary that includes: **IMPORTANT**: You must ALWAYS post a comment with your findings, even if you did not find any relevant information. If you didn't find anything useful, explain what you searched for and why no relevant results were found. -**Report Formatting**: Use h3 (###) or lower for all headers in the report to maintain proper document hierarchy. Wrap long sections in `
Section Name` tags to improve readability. +**Report Formatting**: Use h3 (###) or lower for all headers in the report to maintain proper document hierarchy. Wrap long sections in `
Section Name` tags to improve readability. Your research summary should be formatted as a comment with: @@ -148,7 +148,7 @@ Your research summary should be formatted as a comment with: [Brief overview of key findings - or state that no relevant findings were discovered]
-Click to expand detailed findings +Click to expand detailed findings ### Research Findings diff --git a/.github/workflows/sergo.md b/.github/workflows/sergo.md index 6fe4f749db7..7dc52ac36a1 100644 --- a/.github/workflows/sergo.md +++ b/.github/workflows/sergo.md @@ -465,7 +465,7 @@ EOF [List medium priority findings]
-Low Priority Issues +Low Priority Issues [List low priority findings in collapsed section] diff --git a/.github/workflows/shared/reporting.md b/.github/workflows/shared/reporting.md index bc08afb42be..72d61b434ef 100644 --- a/.github/workflows/shared/reporting.md +++ b/.github/workflows/shared/reporting.md @@ -13,7 +13,7 @@ When creating GitHub issues or discussions: - 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.** +**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) @@ -26,7 +26,7 @@ Always keep critical information visible (summary, critical issues, key metrics) 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 +3. **Details**: Use `
Section Name` for expanded content 4. **Context**: Add helpful metadata (workflow run, date, trigger) ### Design Principles (Airbnb-Inspired) @@ -49,14 +49,14 @@ Reports should: [Always visible - these are important]
-View Detailed Results +View Detailed Results [Comprehensive details, logs, traces]
-View All Warnings +View All Warnings [Minor issues and potential problems] diff --git a/.github/workflows/smoke-claude.lock.yml b/.github/workflows/smoke-claude.lock.yml index d87967f1d84..5934621dbf7 100644 --- a/.github/workflows/smoke-claude.lock.yml +++ b/.github/workflows/smoke-claude.lock.yml @@ -443,7 +443,7 @@ jobs: - 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.** + **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) @@ -456,7 +456,7 @@ jobs: 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 + 3. **Details**: Use `
Section Name` for expanded content 4. **Context**: Add helpful metadata (workflow run, date, trigger) ### Design Principles (Airbnb-Inspired) @@ -479,14 +479,14 @@ jobs: [Always visible - these are important]
- View Detailed Results + View Detailed Results [Comprehensive details, logs, traces]
- View All Warnings + View All Warnings [Minor issues and potential problems] diff --git a/.github/workflows/step-name-alignment.md b/.github/workflows/step-name-alignment.md index ad81bd3819e..30d6b4f9c27 100644 --- a/.github/workflows/step-name-alignment.md +++ b/.github/workflows/step-name-alignment.md @@ -249,7 +249,7 @@ 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. +**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 diff --git a/.github/workflows/typist.md b/.github/workflows/typist.md index 86b08582641..92649be3aa4 100644 --- a/.github/workflows/typist.md +++ b/.github/workflows/typist.md @@ -224,7 +224,7 @@ Create a comprehensive discussion with your findings. - Overall impact and priority of recommendations]
-Full Analysis Report +Full Analysis Report ## Duplicated Type Definitions diff --git a/.github/workflows/weekly-editors-health-check.md b/.github/workflows/weekly-editors-health-check.md index 3e5c6c44a5f..8446458b28d 100644 --- a/.github/workflows/weekly-editors-health-check.md +++ b/.github/workflows/weekly-editors-health-check.md @@ -118,7 +118,7 @@ Example body (rows reflect whatever editors were discovered in Step 0): ### Editor Health Report โ€“
-Editor Status & Screenshots +Editor Status & Screenshots | Editor | URL | Status | Preview | |--------|-----|--------|---------| diff --git a/.github/workflows/weekly-safe-outputs-spec-review.md b/.github/workflows/weekly-safe-outputs-spec-review.md index 1b0ab97de69..4a08f30b2cf 100644 --- a/.github/workflows/weekly-safe-outputs-spec-review.md +++ b/.github/workflows/weekly-safe-outputs-spec-review.md @@ -192,7 +192,7 @@ Updates the Safe Outputs conformance checker script to align with recent specifi [List git commits or specific changes reviewed]
-๐Ÿ“‹ Script Updates & Testing Details +๐Ÿ“‹ Script Updates & Testing Details ### Script Updates diff --git a/.github/workflows/workflow-normalizer.md b/.github/workflows/workflow-normalizer.md index 0b818359b6d..e7fecff841a 100644 --- a/.github/workflows/workflow-normalizer.md +++ b/.github/workflows/workflow-normalizer.md @@ -54,7 +54,7 @@ Based on the agentic workflows guidelines and Airbnb's design principles of crea 2. **Progressive Disclosure**: Use HTML `
` and `` tags to collapse long content - โŒ Bad: Long lists of items that force scrolling - - โœ… Good: `
View Full Details` wrapping content + - โœ… Good: `
View Full Details` wrapping content - Make summaries bold: `Text` 3. **Checkboxes**: Use proper markdown checkbox syntax @@ -131,12 +131,12 @@ For each workflow listed above, update the prompt to include these formatting gu Add instruction: "Use h3 (###) or lower for all headers in your report to maintain proper document hierarchy." #### 2. Progressive Disclosure -Add instruction: "Wrap long sections in `
Section Name` tags to improve readability and reduce scrolling." +Add instruction: "Wrap long sections in `
Section Name` tags to improve readability and reduce scrolling." Example: \`\`\`markdown
-Full Analysis Details +Full Analysis Details [Long detailed content here...] @@ -203,7 +203,7 @@ Create a summary comment or discussion showing: - โš ๏ธ **Needs Improvement**: [NUMBER] workflows need updates
-View Detailed Findings +View Detailed Findings ### Non-Compliant Workflows diff --git a/.github/workflows/workflow-skill-extractor.md b/.github/workflows/workflow-skill-extractor.md index 6b656ba3841..daafb02f967 100644 --- a/.github/workflows/workflow-skill-extractor.md +++ b/.github/workflows/workflow-skill-extractor.md @@ -345,7 +345,7 @@ Create a comprehensive report as a GitHub Discussion with the following structur ### Recommendation 1: [Skill Name]
-Full Details +Full Details **Current State:** [Code snippets showing current usage] diff --git a/actions/setup/js/gateway_difc_filtered.cjs b/actions/setup/js/gateway_difc_filtered.cjs index d7ba5fbccd6..623df6bdc5a 100644 --- a/actions/setup/js/gateway_difc_filtered.cjs +++ b/actions/setup/js/gateway_difc_filtered.cjs @@ -94,7 +94,7 @@ function generateDifcFilteredSection(filteredEvents) { let section = "\n\n> [!NOTE]\n"; section += `>
\n`; - section += `> ๐Ÿ”’ Integrity filter blocked ${count} ${itemWord}\n`; + section += `> ๐Ÿ”’ Integrity filter blocked ${count} ${itemWord}\n`; section += `>\n`; section += `> The following ${itemWord} were blocked because they don't meet the GitHub integrity level.\n`; section += `>\n`; diff --git a/actions/setup/js/gateway_difc_filtered.test.cjs b/actions/setup/js/gateway_difc_filtered.test.cjs index 9f4ba9cda0c..71456ee6785 100644 --- a/actions/setup/js/gateway_difc_filtered.test.cjs +++ b/actions/setup/js/gateway_difc_filtered.test.cjs @@ -175,7 +175,7 @@ describe("gateway_difc_filtered.cjs", () => { expect(result).toContain("> [!NOTE]"); expect(result).toContain(">
"); expect(result).toContain(">
"); - expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 1 item"); + expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 1 item"); expect(result).toContain("[#42](https://github.com/org/repo/issues/42)"); expect(result).toContain("`list_issues`"); expect(result).toContain("Integrity check failed"); @@ -202,7 +202,7 @@ describe("gateway_difc_filtered.cjs", () => { const result = generateDifcFilteredSection(events); expect(result).toContain("> [!NOTE]"); - expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 2 items"); + expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 2 items"); expect(result).toContain("[#42](https://github.com/org/repo/issues/42)"); expect(result).toContain("[#99](https://github.com/org/repo/issues/99)"); }); @@ -318,7 +318,7 @@ describe("gateway_difc_filtered.cjs", () => { const result = generateDifcFilteredSection(events); - expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 2 items"); + expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 2 items"); expect(result).toContain("[#42](https://github.com/org/repo/issues/42)"); expect(result).toContain("[#99](https://github.com/org/repo/issues/99)"); }); @@ -363,7 +363,7 @@ describe("gateway_difc_filtered.cjs", () => { const result = generateDifcFilteredSection(events); // Summary still shows the total count - expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 20 items"); + expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 20 items"); // First 16 items rendered expect(result).toContain("[#1](https://github.com/org/repo/issues/1)"); expect(result).toContain("[#16](https://github.com/org/repo/issues/16)"); @@ -418,7 +418,7 @@ describe("gateway_difc_filtered.cjs", () => { const result = generateDifcFilteredSection(events); // Both entries should be shown; #unknown text hidden, tool_name used instead - expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 2 items"); + expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 2 items"); expect(result).not.toContain("#unknown"); expect(result).toContain("`search_issues`"); expect(result).toContain("[#42](https://github.com/org/repo/issues/42)"); @@ -436,7 +436,7 @@ describe("gateway_difc_filtered.cjs", () => { const result = generateDifcFilteredSection(events); - expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 1 item"); + expect(result).toContain("> ๐Ÿ”’ Integrity filter blocked 1 item"); expect(result).toContain("`search_issues`"); expect(result).not.toContain("#unknown"); }); diff --git a/actions/setup/js/generate_observability_summary.cjs b/actions/setup/js/generate_observability_summary.cjs index 0f28bb12a48..e28cd13d65c 100644 --- a/actions/setup/js/generate_observability_summary.cjs +++ b/actions/setup/js/generate_observability_summary.cjs @@ -80,7 +80,7 @@ function buildObservabilitySummary(data) { const lines = []; lines.push("
"); - lines.push("Observability"); + lines.push("Observability"); lines.push(""); if (data.workflowName) { diff --git a/actions/setup/js/generate_observability_summary.test.cjs b/actions/setup/js/generate_observability_summary.test.cjs index 56d7a06a8c2..b3029b78758 100644 --- a/actions/setup/js/generate_observability_summary.test.cjs +++ b/actions/setup/js/generate_observability_summary.test.cjs @@ -54,7 +54,7 @@ describe("generate_observability_summary.cjs", () => { expect(mockCore.summary.addRaw).toHaveBeenCalledTimes(1); const summary = mockCore.summary.addRaw.mock.calls[0][0]; - expect(summary).toContain("Observability"); + expect(summary).toContain("Observability"); expect(summary).toContain("- **workflow**: triage-workflow"); expect(summary).toContain("- **engine**: copilot"); expect(summary).toContain("- **trace id**: trace-123"); diff --git a/actions/setup/js/handle_agent_failure.cjs b/actions/setup/js/handle_agent_failure.cjs index 9e98170674b..d3bad3cce68 100644 --- a/actions/setup/js/handle_agent_failure.cjs +++ b/actions/setup/js/handle_agent_failure.cjs @@ -370,7 +370,7 @@ function buildCodePushFailureContext(codePushFailureErrors, pullRequest = null, yamlSnippet += ` ${yamlKey}:\n protected-files: fallback-to-issue\n`; } yamlSnippet += "```\n"; - context += "\n
\nโš™๏ธ Configure protected-files: fallback-to-issue\n\n"; + context += "\n
\nโš™๏ธ Configure protected-files: fallback-to-issue\n\n"; context += yamlSnippet; context += "
\n"; } @@ -421,7 +421,7 @@ function buildCodePushFailureContext(codePushFailureErrors, pullRequest = null, } } - context += "\n
\n๐Ÿ“‹ Apply the patch manually\n\n"; + context += "\n
\n๐Ÿ“‹ Apply the patch manually\n\n"; if (runId) { context += `\`\`\`sh # Download the patch artifact from the workflow run diff --git a/actions/setup/js/handle_noop_message.test.cjs b/actions/setup/js/handle_noop_message.test.cjs index b5eba9408f3..b52ae831124 100644 --- a/actions/setup/js/handle_noop_message.test.cjs +++ b/actions/setup/js/handle_noop_message.test.cjs @@ -27,7 +27,7 @@ describe("handle_noop_message", () => { return `This issue tracks all no-op runs from agentic workflows in this repository. Each workflow run that completes with a no-op message (indicating no action was needed) posts a comment here.
-๐Ÿ“˜ What is a No-Op? +๐Ÿ“˜ What is a No-Op? A no-op (no operation) occurs when an agentic workflow runs successfully but determines that no action is required. For example: - A security scanner that finds no issues @@ -39,7 +39,7 @@ These are successful outcomes, not failures, and help provide transparency into
-๐ŸŽฏ How This Helps +๐ŸŽฏ How This Helps This issue helps you: - Track workflows that ran but determined no action was needed @@ -49,7 +49,7 @@ This issue helps you:
-๐Ÿ“š Resources +๐Ÿ“š Resources - [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw) diff --git a/actions/setup/js/missing_info_formatter.cjs b/actions/setup/js/missing_info_formatter.cjs index afee78f2054..8bdc8b8ab78 100644 --- a/actions/setup/js/missing_info_formatter.cjs +++ b/actions/setup/js/missing_info_formatter.cjs @@ -79,7 +79,7 @@ function generateMissingToolsSection(missingTools) { if (!missingTools || missingTools.length === 0) return ""; const content = formatMissingTools(missingTools); - return `\n\n
\nMissing Tools\n\n${content}\n\n
`; + return `\n\n
\nMissing Tools\n\n${content}\n\n
`; } /** @@ -91,7 +91,7 @@ function generateMissingDataSection(missingData) { if (!missingData || missingData.length === 0) return ""; const content = formatMissingData(missingData); - return `\n\n
\nMissing Data\n\n${content}\n\n
`; + return `\n\n
\nMissing Data\n\n${content}\n\n
`; } /** @@ -103,7 +103,7 @@ function generateNoopMessagesSection(noopMessages) { if (!noopMessages?.length) return ""; const content = formatNoopMessages(noopMessages); - return `\n\n
\nNo-Op Messages\n\n${content}\n\n
`; + return `\n\n
\nNo-Op Messages\n\n${content}\n\n
`; } /** diff --git a/actions/setup/js/missing_info_formatter.test.cjs b/actions/setup/js/missing_info_formatter.test.cjs index ad9af95d704..0283699127b 100644 --- a/actions/setup/js/missing_info_formatter.test.cjs +++ b/actions/setup/js/missing_info_formatter.test.cjs @@ -94,7 +94,7 @@ describe("missing_info_formatter.cjs", () => { const result = generateMissingToolsSection(tools); expect(result).toContain("
"); - expect(result).toContain("Missing Tools"); + expect(result).toContain("Missing Tools"); expect(result).toContain("**docker**"); expect(result).toContain("
"); }); @@ -113,7 +113,7 @@ describe("missing_info_formatter.cjs", () => { const result = generateMissingDataSection(data); expect(result).toContain("
"); - expect(result).toContain("Missing Data"); + expect(result).toContain("Missing Data"); expect(result).toContain("**api\\_key**"); expect(result).toContain("
"); }); @@ -170,7 +170,7 @@ describe("missing_info_formatter.cjs", () => { const result = generateNoopMessagesSection(messages); expect(result).toContain("
"); - expect(result).toContain("No-Op Messages"); + expect(result).toContain("No-Op Messages"); expect(result).toContain("No action required"); expect(result).toContain("
"); }); diff --git a/actions/setup/js/parse_mcp_gateway_log.cjs b/actions/setup/js/parse_mcp_gateway_log.cjs index e91bacf600e..aae854a8961 100644 --- a/actions/setup/js/parse_mcp_gateway_log.cjs +++ b/actions/setup/js/parse_mcp_gateway_log.cjs @@ -243,7 +243,7 @@ function generateDifcFilteredSummary(filteredEvents) { const lines = []; lines.push("
"); - lines.push(`๐Ÿ”’ DIFC Filtered Events (${filteredEvents.length})\n`); + lines.push(`๐Ÿ”’ DIFC Filtered Events (${filteredEvents.length})\n`); lines.push(""); lines.push("The following tool calls were blocked by DIFC integrity or secrecy checks:\n"); lines.push(""); @@ -347,7 +347,7 @@ function generateRpcMessagesSummary(entries, difcFilteredEvents) { const blockedNote = blockedCount > 0 ? `, ${blockedCount} blocked` : ""; const callLines = []; callLines.push("
"); - callLines.push(`MCP Gateway Activity (${requests.length} request${requests.length !== 1 ? "s" : ""}${blockedNote})\n`); + callLines.push(`MCP Gateway Activity (${requests.length} request${requests.length !== 1 ? "s" : ""}${blockedNote})\n`); callLines.push(""); callLines.push("| Time | Server | Tool / Method |"); callLines.push("|------|--------|---------------|"); @@ -364,7 +364,7 @@ function generateRpcMessagesSummary(entries, difcFilteredEvents) { parts.push(callLines.join("\n")); } else if (blockedCount > 0) { // No requests, but there are DIFC_FILTERED events โ€” add a minimal header - parts.push(`
\nMCP Gateway Activity (${blockedCount} blocked)\n\n*All tool calls were blocked by the integrity filter.*\n\n
\n`); + parts.push(`
\nMCP Gateway Activity (${blockedCount} blocked)\n\n*All tool calls were blocked by the integrity filter.*\n\n
\n`); } // Other message types (not REQUEST, RESPONSE, DIFC_FILTERED) @@ -375,7 +375,7 @@ function generateRpcMessagesSummary(entries, difcFilteredEvents) { typeCounts[entry.type] = (typeCounts[entry.type] || 0) + 1; } const otherLines = Object.entries(typeCounts).map(([type, count]) => `- **${type}**: ${count} message${count !== 1 ? "s" : ""}`); - parts.push("
\nOther Gateway Messages\n\n" + otherLines.join("\n") + "\n\n
\n"); + parts.push("
\nOther Gateway Messages\n\n" + otherLines.join("\n") + "\n\n
\n"); } // DIFC_FILTERED section (re-uses existing table renderer) @@ -593,7 +593,7 @@ function generateGatewayLogSummary(gatewayLogContent, stderrLogContent) { // Add gateway.log if it has content if (gatewayLogContent && gatewayLogContent.trim().length > 0) { summary.push("
"); - summary.push("MCP Gateway Log (gateway.log)\n"); + summary.push("MCP Gateway Log (gateway.log)\n"); summary.push("```"); summary.push(gatewayLogContent.trim()); summary.push("```"); @@ -603,7 +603,7 @@ function generateGatewayLogSummary(gatewayLogContent, stderrLogContent) { // Add stderr.log if it has content if (stderrLogContent && stderrLogContent.trim().length > 0) { summary.push("
"); - summary.push("MCP Gateway Log (stderr.log)\n"); + summary.push("MCP Gateway Log (stderr.log)\n"); summary.push("```"); summary.push(stderrLogContent.trim()); summary.push("```"); diff --git a/actions/setup/js/parse_mcp_gateway_log.test.cjs b/actions/setup/js/parse_mcp_gateway_log.test.cjs index c69b7e1bf3c..673ff75be80 100644 --- a/actions/setup/js/parse_mcp_gateway_log.test.cjs +++ b/actions/setup/js/parse_mcp_gateway_log.test.cjs @@ -170,12 +170,12 @@ Some content here.`; const summary = generateGatewayLogSummary(gatewayLogContent, stderrLogContent); // Check gateway.log section - expect(summary).toContain("MCP Gateway Log (gateway.log)"); + expect(summary).toContain("MCP Gateway Log (gateway.log)"); expect(summary).toContain("Gateway started"); expect(summary).toContain("Server listening on port 8080"); // Check stderr.log section - expect(summary).toContain("MCP Gateway Log (stderr.log)"); + expect(summary).toContain("MCP Gateway Log (stderr.log)"); expect(summary).toContain("Debug: connection accepted"); expect(summary).toContain("Debug: request processed"); @@ -191,9 +191,9 @@ Some content here.`; const summary = generateGatewayLogSummary(gatewayLogContent, stderrLogContent); - expect(summary).toContain("MCP Gateway Log (gateway.log)"); + expect(summary).toContain("MCP Gateway Log (gateway.log)"); expect(summary).toContain("Gateway started"); - expect(summary).not.toContain("MCP Gateway Log (stderr.log)"); + expect(summary).not.toContain("MCP Gateway Log (stderr.log)"); }); test("generates summary with only stderr.log content", () => { @@ -202,8 +202,8 @@ Some content here.`; const summary = generateGatewayLogSummary(gatewayLogContent, stderrLogContent); - expect(summary).not.toContain("MCP Gateway Log (gateway.log)"); - expect(summary).toContain("MCP Gateway Log (stderr.log)"); + expect(summary).not.toContain("MCP Gateway Log (gateway.log)"); + expect(summary).toContain("MCP Gateway Log (stderr.log)"); expect(summary).toContain("Error: connection failed"); }); diff --git a/actions/setup/md/agent_failure_issue.md b/actions/setup/md/agent_failure_issue.md index b636eb9e82c..4806f6d0ab5 100644 --- a/actions/setup/md/agent_failure_issue.md +++ b/actions/setup/md/agent_failure_issue.md @@ -11,7 +11,7 @@ **Assign this issue to Copilot** using the `agentic-workflows` sub-agent to automatically debug and fix the workflow failure.
-Debug with any coding agent +Debug with any coding agent Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.): @@ -24,7 +24,7 @@ The failed workflow run is at {run_url}
-Manually invoke the agent +Manually invoke the agent Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt. @@ -36,7 +36,7 @@ Debug this workflow failure using your favorite Agent CLI and the `agentic-workf > [!TIP] >
-> Stop reporting this workflow as a failure +> Stop reporting this workflow as a failure > > To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter: > ```yaml diff --git a/actions/setup/md/manifest_protection_push_failed_fallback.md b/actions/setup/md/manifest_protection_push_failed_fallback.md index 84866b31446..8520f17502a 100644 --- a/actions/setup/md/manifest_protection_push_failed_fallback.md +++ b/actions/setup/md/manifest_protection_push_failed_fallback.md @@ -17,7 +17,7 @@ >
-Create the pull request manually +Create the pull request manually ```sh # Download the patch from the workflow run diff --git a/actions/setup/md/manifest_protection_push_to_pr_fallback.md b/actions/setup/md/manifest_protection_push_to_pr_fallback.md index 9a9d120eb1e..f664113f496 100644 --- a/actions/setup/md/manifest_protection_push_to_pr_fallback.md +++ b/actions/setup/md/manifest_protection_push_to_pr_fallback.md @@ -17,7 +17,7 @@ ---
-Apply the patch after review +Apply the patch after review The patch is available in the workflow run artifacts: diff --git a/actions/setup/md/noop_runs_issue.md b/actions/setup/md/noop_runs_issue.md index 69d96161b97..423c1975a6a 100644 --- a/actions/setup/md/noop_runs_issue.md +++ b/actions/setup/md/noop_runs_issue.md @@ -1,7 +1,7 @@ This issue tracks all no-op runs from agentic workflows in this repository. Each workflow run that completes with a no-op message (indicating no action was needed) posts a comment here.
-What is a No-Op? +What is a No-Op? A no-op (no operation) occurs when an agentic workflow runs successfully but determines that no action is required. For example: - A security scanner that finds no issues @@ -13,7 +13,7 @@ These are successful outcomes, not failures, and help provide transparency into
-How This Helps +How This Helps This issue helps you: - Track workflows that ran but determined no action was needed @@ -23,7 +23,7 @@ This issue helps you:
-Resources +Resources - [GitHub Agentic Workflows Documentation](https://github.com/github/gh-aw) diff --git a/pkg/workflow/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md b/pkg/workflow/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md index c81c58d08b0..5e2936d214f 100644 --- a/pkg/workflow/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md +++ b/pkg/workflow/.github/aw/imports/githubnext/agentics/d3422bf940923ef1d43db5559652b8e1e71869f3/workflows_shared_reporting.md @@ -8,7 +8,7 @@ Structure your report with an overview followed by detailed content: 1. **Content Overview**: Start with 1-2 paragraphs that summarize the key findings, highlights, or main points of your report. This should give readers a quick understanding of what the report contains without needing to expand the details. -2. **Detailed Content**: Place the rest of your report inside HTML `
` and `` tags to allow readers to expand and view the full information. **IMPORTANT**: Always wrap the summary text in `` tags to make it bold. +2. **Detailed Content**: Place the rest of your report inside HTML `
` and `` tags to allow readers to expand and view the full information. **Example format:** @@ -18,7 +18,7 @@ Brief overview paragraph 1 introducing the report and its main findings. Optional overview paragraph 2 with additional context or highlights.
-Full Report Details +Full Report Details ## Detailed Analysis diff --git a/pkg/workflow/testdata/wasm_golden/fixtures/shared/reporting.md b/pkg/workflow/testdata/wasm_golden/fixtures/shared/reporting.md index bc08afb42be..72d61b434ef 100644 --- a/pkg/workflow/testdata/wasm_golden/fixtures/shared/reporting.md +++ b/pkg/workflow/testdata/wasm_golden/fixtures/shared/reporting.md @@ -13,7 +13,7 @@ When creating GitHub issues or discussions: - 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.** +**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) @@ -26,7 +26,7 @@ Always keep critical information visible (summary, critical issues, key metrics) 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 +3. **Details**: Use `
Section Name` for expanded content 4. **Context**: Add helpful metadata (workflow run, date, trigger) ### Design Principles (Airbnb-Inspired) @@ -49,14 +49,14 @@ Reports should: [Always visible - these are important]
-View Detailed Results +View Detailed Results [Comprehensive details, logs, traces]
-View All Warnings +View All Warnings [Minor issues and potential problems] diff --git a/scratchpad/gastown.md b/scratchpad/gastown.md index adc728eb141..42fd9574807 100644 --- a/scratchpad/gastown.md +++ b/scratchpad/gastown.md @@ -566,7 +566,7 @@ imports: Use HTML details/summary for collapsible sections:
-๐Ÿ“Š Full Report Details +๐Ÿ“Š Full Report Details [Report content here] diff --git a/scratchpad/token-budget-guidelines.md b/scratchpad/token-budget-guidelines.md index 982b0f2537e..4649f8f4e27 100644 --- a/scratchpad/token-budget-guidelines.md +++ b/scratchpad/token-budget-guidelines.md @@ -306,7 +306,7 @@ Test a representative subset of 6-8 scenarios to reduce token consumption... ```markdown ### Key Findings (3-5 bullet points max)
-View Detailed Scenario Analysis +View Detailed Scenario Analysis [Detailed content hidden by default]
``` @@ -334,7 +334,7 @@ Use HTML `
` tags to reduce initial output verbosity: ```markdown
-View Detailed Examples +View Detailed Examples [Verbose content that AI generates once but doesn't repeatedly reference]