pr/issue show: include discussion comments #29

New issue

Open

opened 2026-05-20 08:38:20 +02:00 by heiko · 1 comment

heiko commented

2026-05-20 08:38:20 +02:00

Owner

Gap

fj pr show <n> and fj issue show <n> render the body of a PR/issue but omit
the discussion comments. To read review feedback or follow-up discussion, the
user has to fall back to curl against the Forgejo API:

curl -sS -H "Authorization: token …" \
  https://<host>/api/v1/repos/<owner>/<repo>/issues/<n>/comments \
  | jq -r '.[] | "--- @\(.user.login) at \(.created_at) ---\n\(.body)"'

This makes fj insufficient as a one-stop tool for code review workflows and
forces a fallback every time a PR has feedback.

Desired behaviour

Append a Comments section to the existing show output:

…existing body…

---

## Comments

### @reviewer at 2026-05-20T08:23:57+02:00

<comment body>

### @other-reviewer at …

<comment body>

A flag like --no-comments would let scripts opt out of the extra API call.

Relation to #23

Issue #23 covers posting comments via fj pr/issue comment. This issue is
specifically about reading them inline with show; the two are
complementary and can be implemented independently.

Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com

## Gap `fj pr show <n>` and `fj issue show <n>` render the body of a PR/issue but omit the discussion comments. To read review feedback or follow-up discussion, the user has to fall back to `curl` against the Forgejo API: ``` curl -sS -H "Authorization: token …" \ https://<host>/api/v1/repos/<owner>/<repo>/issues/<n>/comments \ | jq -r '.[] | "--- @\(.user.login) at \(.created_at) ---\n\(.body)"' ``` This makes `fj` insufficient as a one-stop tool for code review workflows and forces a fallback every time a PR has feedback. ## Desired behaviour Append a *Comments* section to the existing `show` output: ``` …existing body… --- ## Comments ### @reviewer at 2026-05-20T08:23:57+02:00 <comment body> ### @other-reviewer at … <comment body> ``` A flag like `--no-comments` would let scripts opt out of the extra API call. ## Relation to #23 Issue #23 covers *posting* comments via `fj pr/issue comment`. This issue is specifically about *reading* them inline with `show`; the two are complementary and can be implemented independently. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

heiko added the

Kind/Enhancement

label

2026-05-20 08:38:20 +02:00

heiko commented

2026-05-22 11:38:32 +02:00

Author

Owner

AI attribution comment added per repository instruction for this open issue.\n\n(co)authored by ai:gpt-5-codex

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

heiko/fj#29

No description provided.

Rows
Columns