Incorrect commit counts from updater on shallow installs
Cluster 53479 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #86318 on 14 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #86318. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86318. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern the CLI update command reporting misleading numbers of new commits (e.g. 'Found 9980 new commit(s)') on shallow or diverged git installs, apparently because it relies on rev-list counts. One member describes the problem, and the others are titled as proposed fixes to avoid or skip those counts; their outcomes are not stated.
Open issues0
Open PRs0
Fixes on record
-
#86318 fix(update): stop reporting bogus 'Found 9980 new commit(s)' on shallow installs
files:
hermes_cli/update_cmd.py,tests/hermes_cli/test_update_apply_shallow_count.py
2 PRs closed without merging
From the close comments: duplicate 2
Closed issues · 1
- Closed#53479CLI updater still trusts rev-list counts for shallow/diverged installs
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #86318
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 14 Aug 2026