Cairn

Kanban PR acceptance: classify unreadable repo errors as auth

NousResearch/hermes-agent · cluster 129579 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

The members concern how Kanban PR acceptance categorizes gh failures, specifically an unreadable private repo being reported as an infrastructure error rather than an authentication one. Two titles are fix-style changes touching gh GraphQL exit handling and profile auth retention, and one is a bug report; their outcomes are not stated here.

Open issues1

  • Issue#129579[Bug]: Kanban PR acceptance reports unreadable private repo as infra, not auth

Open PRs2

  • PR#116139fix(kanban): type gh acceptance failures without dropping profile auth
  • PR#129580fix(kanban): classify unreadable PR repo as auth on gh GraphQL exit
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/129579.json
cluster/129579.md