Feature Request: Improve MR Thread Visibility and Context

Problem to solve

What I'm trying to do: I'm working on merge requests through the CLI and need to review and resolve discussion threads. The only way I've found to see unresolved threads is using glab mr view <id> --comments --output json, but it's not very readable.

The problem: The JSON output isn't human-readable - text output would be much more appropriate. I can (and do) use tools like jq to parse it, but it's way too cumbersome to do this every time I want to check on thread status. I need enough context to understand and resolve the threads without all the JSON parsing overhead.

What's missing:

  • No human-readable text output for discussion threads
  • Can't easily see which threads are unresolved
  • Line numbers and file context aren't presented clearly
  • Have to use jq or similar tools every time, which is tedious

Proposal

  • Add more context, like line numbers, when using text output
  • Create a dedicated command for threads

Further details

What I'm trying to do: I'm working on merge requests through the CLI and need to review and resolve discussion threads. The only way I've found to see unresolved threads is using glab mr view <id> --comments --output json, but it's not very readable.

The problem: The JSON output isn't human-readable - text output would be much more appropriate. I can (and do) use tools like jq to parse it, but it's way too cumbersome to do this every time I want to check on thread status. I need enough context to understand and resolve the threads without all the JSON parsing overhead.

What's missing:

  • No human-readable text output for discussion threads
  • Can't easily see which threads are unresolved
  • Line numbers and file context aren't presented clearly
  • Have to use jq or similar tools every time, which is tedious

Links / references

Relates to #7610