docs: add run failure issues and no-op report sections to monitoring guide#16847
Merged
docs: add run failure issues and no-op report sections to monitoring guide#16847
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update documentation on agentic maintenance
docs: add run failure issues and no-op report sections to monitoring guide
Feb 19, 2026
pelikhan
approved these changes
Feb 19, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the monitoring pattern documentation by adding comprehensive coverage of operational features for agent failure tracking and no-op run reporting, plus updates the agent factory status page to include the new "Smoke macOS ARM64" workflow.
Changes:
- Documents run failure issue generation via
create-issueand sub-issue grouping withgroup-reports - Documents no-op run reporting behavior and how to control it using
report-as-issue - Adds "Smoke macOS ARM64" workflow entry to agent factory status table
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/src/content/docs/patterns/monitoring.md | Adds two new sections documenting run failure issues (with sub-issue grouping) and no-op run reports (with control options) |
| docs/src/content/docs/agent-factory-status.mdx | Adds new "Smoke macOS ARM64" workflow entry to the experimental workflows table |
| .github/workflows/smoke-macos-arm64.lock.yml | Improves step naming consistency: capitalizes "Safe Inputs" and changes "Echo" to "Print" |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced Feb 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The monitoring pattern page lacked documentation on two operational features: automatic failure issue generation and no-op run reporting.
Changes
docs/src/content/docs/patterns/monitoring.mdRun failure issues — documents how to surface agent failures as GitHub issues via
create-issue, including howgroup-reports: truelinks each failure as a sub-issue under a shared "[agentics] Failed runs" parent (max 64 sub-issues):No-op run reports — documents default behavior (no-op messages posted as issue comments) and how to suppress it without losing step summary visibility:
Both sections link to the relevant anchors in the Safe Outputs reference.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
telemetry.astro.build/opt/hostedtoolcache/node/24.13.1/x64/bin/node node /home/REDACTED/work/gh-aw/gh-aw/docs/node_modules/.bin/astro build(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.