fix: silence Dagger output in deploy tasks, only show on failure #390

2026-06-04T00:27:06Z

guettlibot commented

2026-06-04 00:27:06 +00:00

(Migrated from codeberg.org)

Summary

Wraps the `dagger call` in `deploy-linux`, `publish-android`, and `deploy-apk` Taskfile tasks with `scripts/silent_on_success.sh`
On success: no Dagger output is printed (eliminates the verbose logs seen in deploy.yml CI runs)
On failure: full Dagger output is replayed so errors remain visible

The project already uses `scripts/silent_on_success.sh` for other noisy commands (fvm, flutter pub get, build_runner, etc.) — this applies the same pattern to the three deploy tasks called from `.forgejo/workflows/deploy.yml`.

Closes #389

Test plan

Verify deploy CI run produces significantly less output on success
Verify that on a failure, the full Dagger output is still printed

🤖 Generated with Claude Code

## Summary - Wraps the \`dagger call\` in \`deploy-linux\`, \`publish-android\`, and \`deploy-apk\` Taskfile tasks with \`scripts/silent_on_success.sh\` - On success: no Dagger output is printed (eliminates the verbose logs seen in deploy.yml CI runs) - On failure: full Dagger output is replayed so errors remain visible The project already uses \`scripts/silent_on_success.sh\` for other noisy commands (fvm, flutter pub get, build_runner, etc.) — this applies the same pattern to the three deploy tasks called from \`.forgejo/workflows/deploy.yml\`. Closes #389 ## Test plan - [ ] Verify deploy CI run produces significantly less output on success - [ ] Verify that on a failure, the full Dagger output is still printed 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: guettli/sharedinbox#390