Both functions use 'set -euo pipefail' in the script passed to
'docker exec ... sh -lc', but /bin/sh on Debian (dash) does not support
-o pipefail, causing all microservice proxy and e2e API calls to fail
with 'sh: 1: set: Illegal option -o pipefail'.
Fix: use bash instead of sh, since bash is available in the container.
Issue 1 of #780: gh pr list --json whitelist is unintuitive.
merged / closedAt / mergedAt / mergeCommit are basic per-PR
fields already returned by GitHub list API and already
projected by prSummary(); they were previously rejected by
the prListJsonFields validator. Add them to PR_LIST_JSON_FIELDS
so callers no longer have to fall back to a pr view per-PR.
mergeable / mergeStateStatus / statusCheckRollup remain
closeout fields that still require a per-PR pr view.
Issue 2 of #780: gh issue close --comment only accepts short
inline text; long Markdown closeout bodies had to escape
backticks, newlines and \\ in shell, then bash heredoc.
Add --comment-file <file|-> to issue close/reopen, which
mirrors the existing --body-file plumbing through
readIssueLifecycleCommentBody. --comment and --comment-file
are mutually exclusive; both remain mutually exclusive with
--body and --body-file.
Verified live:
- gh pr list --repo pikasTech/HWLAB --state closed --json
number,merged,mergedAt,closedAt,mergeCommit returns real data
(number=781 merged=true mergedAt=2026-06-03T14:22:32Z
closedAt=2026-06-03T14:22:32Z
mergeCommit={oid:3ac4cf8d2e4dfadb251cad53bf35d08b86d73840})
- gh pr list --json mergeable,statusCheckRollup still rejected
with 'unsupported closeout field(s)' pointing to pr view
- gh issue close 780 --comment-file /tmp/test-close-comment.md
--dry-run reports comment.planned=true bodyChars=155
bodySource.kind=body-file
- gh issue close 780 --comment 'x' --comment-file /tmp/x.md
--dry-run fails with --comment and --comment-file are
mutually exclusive
Codex