Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 4, 2026

CI jobs were suppressing errors with || true, masking failures. Commands now propagate errors properly for immediate visibility.

Changes

  • Update command: Removed || true from gh-aw update --verbose --no-actions
  • Logs command: Removed || true from gh-aw logs -c 2 --engine copilot --json
  • Security scans: Added --verbose flag to gh-aw compile poem-bot for debugging output
# Before: Errors silently ignored
./gh-aw update --verbose --no-actions || true

# After: Errors propagate to CI
./gh-aw update --verbose --no-actions

Jobs now fail fast when commands fail, preventing silent errors from going unnoticed.

Original prompt

Reference: https://github.com/githubnext/gh-aw/actions/runs/20693089167/job/59404068768#step:6:1

Configure script to propagate errors
Remove | true
Use verbose mode for gh-aw


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

- Remove || true from update command to propagate errors (line 260)
- Remove || true from logs command to propagate errors (line 757)
- Add --verbose flag to compile command for better debugging (line 728)

This ensures CI fails when these commands fail, making issues more visible.

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot AI changed the title [WIP] Configure script to propagate errors and enable verbose mode Remove error suppression and add verbose mode in CI workflows Jan 4, 2026
Copilot AI requested a review from pelikhan January 4, 2026 13:07
@pelikhan pelikhan marked this pull request as ready for review January 4, 2026 13:09
@pelikhan pelikhan merged commit 309b85e into main Jan 4, 2026
4 checks passed
@pelikhan pelikhan deleted the copilot/configure-script-error-propagation branch January 4, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants