Fix inaccurate update reporting for partial clones

NousResearch/hermes-agent · cluster 131298 · 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.

These members address a bug where update operations involving partial-clone or tree:0 checkouts incorrectly report no-op or detached-checkout states due to missing commits and misleading merge behavior. The fixes aim to recover missing commits and improve accuracy of branch update status reporting.

Open issues1

  • Issue#131298[Bug]: hermes update reports a false 'detached checkout' no-op when a tree:0 checkout has a missing commit (merge --ff-only exits 0 without moving HEAD)

Open PRs2

  • PR#131304fix(cli): report branch no-op updates accurately
  • PR#131305fix(update): recover missing partial-clone commits
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.