Stop CI and checks pipelines from swallowing CLI failures #645

New issue

barrettruth · 2026-05-06T19:56:26Z

barrettruth commented

2026-05-06 19:56:26 +00:00

Parent: #634

Problem

Some GitLab and Forgejo CI/check commands use shell pipelines with redirected stderr, fragile pipe status, or jq fallbacks that can turn auth, network, repo, or API failures into empty output. That defeats picker/log error handling because the failure never reaches the shared formatter.

Scope

Audit GitLab and Forgejo CI/check/list/log command builders.
Preserve nonzero CLI/API failures through shell pipelines.
Avoid 2>/dev/null or empty JSON defaults where they erase actionable errors.
Add backend command tests for auth/network/API failure-like stderr.

Non-goals

Do not add new CI features.
Do not redesign CI navigation or schemas.

Parent: #634 ## Problem Some GitLab and Forgejo CI/check commands use shell pipelines with redirected stderr, fragile pipe status, or `jq` fallbacks that can turn auth, network, repo, or API failures into empty output. That defeats picker/log error handling because the failure never reaches the shared formatter. ## Scope - Audit GitLab and Forgejo CI/check/list/log command builders. - Preserve nonzero CLI/API failures through shell pipelines. - Avoid `2>/dev/null` or empty JSON defaults where they erase actionable errors. - Add backend command tests for auth/network/API failure-like stderr. ## Non-goals - Do not add new CI features. - Do not redesign CI navigation or schemas.

barrettruth added the

bug

v0.2.0

labels

2026-05-06 19:56:26 +00:00

barrettruth referenced this issue

2026-05-06 19:56:43 +00:00

Tracker: error handling and edge cases #634

barrettruth referenced this issue from a pull request that will close it,

2026-05-06 22:49:06 +00:00

Preserve CI pipeline failures #657

barrettruth closed this issue