Cairn
NousResearch/hermes-agent

Shallow clone update check false positive fix

Cluster 98214 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

Addresses a bug where --check incorrectly reports an update as available in shallow clones when the GitHub compare API cannot resolve a local-only HEAD SHA. The fix adds a fallback to a local merge-base calculation in that case.

Open issues1

  • Issue#98214update --check: shallow clone with local commits always reports "Update available" when the compare API can't resolve a local-only HEAD SHA

Open PRs1

  • PR#98537fix(cli): fall back to local merge-base when GitHub compare returns None (#98214)

1 PR closed without merging

From the close comments: other 1

  • #98293 fix(update): shallow --check must not report "behind" when the compare API can't resolve a local-only HEAD (#98214) · other
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/98214.json
cluster/98214.md