Reduce setup.sh log verbosity by moving file copy messages to debug level#8692
Merged
Reduce setup.sh log verbosity by moving file copy messages to debug level#8692
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Reduce message verbosity in setup script
Reduce setup.sh log verbosity by moving file copy messages to debug level
Jan 2, 2026
pelikhan
approved these changes
Jan 2, 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
actions/setup/setup.shscript was emitting individual::notice::messages for every file copied (~300+ messages), creating excessive log noise and making workflow runs difficult to scan.Changes
::notice::to::debug::level::notice::level (directory creation, file counts, completion status)Impact
Before:
After:
Reduces notice-level output from ~300 to 10 messages. Individual file names remain available via
::debug::when troubleshooting.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:
https://api.github.com/user/usr/bin/gh gh api user --jq .login go1.25.0 -c=4 -nolocalimports -importcfg /tmp/go-build1392432738/b386/importcfg -pack PGGJ1TVaLT-t env -json GO111MODULE 0.1-go1.25.0.lin-nilfunc GOINSECURE GOMOD GOMODCACHE 0.1-go1.25.0.lin-importcfg(http 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.