fix: use log_step (cyan) for progress messages instead of log_warn (yellow) (#534)

~1500 progress messages across 481 files were using log_warn (yellow)
for normal status updates like "Installing...", "Setting up...",
"Creating server...", etc. This made users think something was wrong
when everything was proceeding normally.

Changes:
- Replace log_warn with log_step for all progress/status messages
- Keep log_warn only for actual warnings (errors, remediation hints)
- Remove emoji from 3 sprite completion messages

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
This commit is contained in:
A 2026-02-11 14:37:43 -08:00 committed by GitHub
parent 800e9ed564
commit 0835b35a36
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
481 changed files with 1602 additions and 1602 deletions

View file

@ -26,7 +26,7 @@ export CODESPACE_NAME
wait_for_codespace "${CODESPACE_NAME}"
log_warn "Installing Continue CLI..."
log_step "Installing Continue CLI..."
run_in_codespace "${CODESPACE_NAME}" "npm install -g @continuedev/cli"
log_info "Continue installed"
@ -37,7 +37,7 @@ else
OPENROUTER_API_KEY=$(get_openrouter_api_key_oauth 5180)
fi
log_warn "Setting up environment variables..."
log_step "Setting up environment variables..."
run_in_codespace "${CODESPACE_NAME}" "printf 'export OPENROUTER_API_KEY=\"%s\"\n' '${OPENROUTER_API_KEY}' >> ~/.bashrc"
run_in_codespace "${CODESPACE_NAME}" "printf 'export OPENROUTER_API_KEY=\"%s\"\n' '${OPENROUTER_API_KEY}' >> ~/.zshrc"
@ -48,7 +48,7 @@ log_info "Codespace setup completed successfully!"
log_info "Codespace: ${CODESPACE_NAME}"
echo ""
log_warn "Starting Continue CLI in TUI mode..."
log_step "Starting Continue CLI in TUI mode..."
sleep 1
clear
gh codespace ssh --codespace "${CODESPACE_NAME}" -- "source ~/.zshrc && cn"