Normalize backend browse and subject-probe failure handling #642

Closed
opened 2026-05-06 19:55:44 +00:00 by barrettruth · 0 comments
Owner

Parent: #634

Problem

Several backend browse/probe paths start CLI commands without callbacks or collapse API failures into generic absence messages. Examples include GitHub/GitLab browse helpers and GitLab subject probes that can turn auth/network failures into no MR or issue found.

Scope

  • Audit backend browse helpers for GitHub, GitLab, and Forgejo.
  • Ensure CLI/API failures are reported when the backend command fails.
  • Distinguish true absence from command/auth/network failure in subject probes.
  • Add backend-specific tests for representative failures.

Non-goals

  • Do not redesign URL generation.
  • Do not add new backend capabilities.
Parent: #634 ## Problem Several backend browse/probe paths start CLI commands without callbacks or collapse API failures into generic absence messages. Examples include GitHub/GitLab browse helpers and GitLab subject probes that can turn auth/network failures into `no MR or issue found`. ## Scope - Audit backend browse helpers for GitHub, GitLab, and Forgejo. - Ensure CLI/API failures are reported when the backend command fails. - Distinguish true absence from command/auth/network failure in subject probes. - Add backend-specific tests for representative failures. ## Non-goals - Do not redesign URL generation. - Do not add new backend capabilities.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
barrettruth/forge.nvim#642
No description provided.