gitsocial pm issue show rejects #commit:hash@branch for an issue in
the current repository.
It only succeeds with the full s3://bucket path prepended, the form
CLI.md reserves for another repository.
Reproduce with gitsocial pm issue create, then gitsocial pm issue
show on the printed #commit reference alone.
CLI.md documents #commit:hash@branch as sufficient for the current
repository.
Expected: gitsocial pm issue show resolves that reference without
the s3 URL.
↩ Max Rakhimov · 2026-09-27
Fixed in #commit:658d9dd7: `gitsocial pm issue show` now resolves a
reference without the repository URL.
These forms now work for an issue in the current repository:
```
#commit:9df57dc74804@gitmsg/pm
#commit:9df57dc74804
9df57dc74804
9df57d
```
An ambiguous prefix gives an error that names two of the matches.
The same fix applies to pm issue comments, comment, edit, close,
reopen, release edit and review pr show. The flags that name an item
(--milestone, --sprint, --parent, --blocks, --blocked-by, --related,
--closes, --depends-on) now also take a prefix, and they store the full
reference.