gitsocial pm issue list in a workspace lists the issues of every
followed repository in the cache, not only the workspace's own and its
registered forks'. In one workspace, 15 of 20 listed issues came from
two followed repositories that are not forks.
Expected: the workspace's issues and its registered forks' issues, as
GetIssuesWithForks names them; another repository's issues with --repo.
↩ Max Rakhimov · 2026-09-27
Fixed in #commit:6a379c80: `pm issue list` now lists the workspace's
issues and its registered forks' issues, not every repository in the
cache. A fork issue that the workspace adopted shows once, as its copy.
`--repo` still lists another repository.
The same scope now applies to every client: `pm status`, the TUI issue
view and issue form, and RPC `pm.getIssues`. Milestone and sprint lists
and pickers read the workspace only.