Merged
Conversation
- Suppress repetitive "Fetched X workflow runs" messages per iteration - Suppress "Processed X/Y runs successfully" per batch - Filter out non-actionable errors (debug logs, JSON fragments, MCP logs) - Filter out invalid tool names (common words, single chars, fragments) - Improve signal-to-noise ratio in error and tool usage tables Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
- Limit error/warning table to top 20 most common issues - Add concise final summary with key metrics - Improve readability of completion message Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Enhance clarity and conciseness of logs command output
Filter noise from logs command output
Jan 5, 2026
pelikhan
approved these changes
Jan 5, 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
logscommand output was cluttered with repetitive progress messages, debug logs, JSON fragments, and invalid tool names, making it difficult to identify actionable information.Changes
Progress messages
Error/warning table
validation completed,executePromptDirectly"errorCodesToRetry","description":[mcp server safeoutputs stderr]::1:56072 - -:- 0.0 NONE_NONE:HIER_NONETool usage table
calls,to,for,Testing,multiple,launches-,aExample
Before:
After:
Implementation
Added
isActionableError()andisValidToolName()filters inpkg/cli/logs_report.go. Modified progress message handling inlogs_github_api.goandlogs_orchestrator.go.Original prompt
Review the output of the "logs" command and make it clearer, more concise, better.