Add dual output to parse agent log files for terminal and step summary#1195
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
- Add write() helper function that outputs to both core.info and core.summary - Update parse_claude_log.cjs to use write() helper - Update parse_codex_log.cjs to use write() helper - Update parse_copilot_log.cjs to use write() helper - Add test for write() helper function - Add test verification that core.info is called with parsed output Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add logging to write output to terminal and summary file
Add write helper to parse agent log files for dual output to terminal and step summary
Oct 3, 2025
- Remove write() helper function from all three parse log files - Inline the calls: core.info(text) and core.summary.addRaw(text).write() - Remove write from module.exports - Remove test for write helper function (no longer needed) - All tests pass (393 JS + Go tests) Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Done. Inlined the write function calls in all three files (parse_claude_log.cjs, parse_codex_log.cjs, parse_copilot_log.cjs). The code now directly calls: core.info(result.markdown);
core.summary.addRaw(result.markdown).write();Commit: f1dd01f |
Copilot
AI
changed the title
Add write helper to parse agent log files for dual output to terminal and step summary
Add dual output to parse agent log files for terminal and step summary
Oct 3, 2025
pelikhan
approved these changes
Oct 3, 2025
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.
Problem
The parse agent log files (
parse_claude_log.cjs,parse_codex_log.cjs,parse_copilot_log.cjs) were only writing output to the GitHub step summary viacore.summary.addRaw(). This meant that parsed agent logs were only visible in the GitHub UI after the workflow completed, but not in the terminal output during workflow execution, making real-time debugging difficult.Solution
Updated all three parse agent log files to write output to both destinations by inlining the calls:
core.info()- visible during workflow run logs in real-timecore.summary.addRaw()- visible in the GitHub UI after completionBefore:
After:
Benefits
Testing
core.infoandcore.summary.addRaware called with parsed outputFiles Modified
pkg/workflow/js/parse_claude_log.cjspkg/workflow/js/parse_codex_log.cjspkg/workflow/js/parse_copilot_log.cjspkg/workflow/js/parse_claude_log.test.cjsFixes #issue-number
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.