Worktree origin branch fixes for tag-pinned narrow checkouts

NousResearch/hermes-agent · cluster 125686

Data as of

Nothing open on GitHub. Fix merged in #126191. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #126191. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #126191. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address failures and fixes when creating worktrees from origin/<branch> on tag-pinned narrow clones. The work covers fetching with correct refspecs, converting origin branches, and branching from the remote tip in this specific checkout configuration.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #126191 fix(worktree): branch from the remote tip on tag-pinned narrow checkouts

    merged to main

    files: apps/desktop/electron/git-worktree-ops.test.ts, apps/desktop/electron/git-worktree-ops.ts, hermes_cli/web_git.py, hermes_cli/worktree_ops.py, tests/hermes_cli/test_web_server_git.py, tests/hermes_cli/test_worktree_sync_base.py

3 PRs closed without merging

From the close comments: merged via another change 2 · superseded by another PR 1

  • #125699 fix(worktree): fetch origin bases with a tracking refspec · merged via another change → #126191, #125712, #125686
  • #125710 Worktrees from origin/<branch> work on tag-pinned narrow checkouts (dashboard, desktop, hermes -w) (#125686) · superseded by another PR → #125699, #125712
  • #125712 fix(worktree): convert an origin/ branch on a tag-pinned narrow clone · merged via another change → #126191, #125699
Closed issues · 1
  • Closed#125686Worktree from origin/<branch> fails on tag-pinned narrow checkouts (dashboard + desktop)
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.40: 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

Merged PRs
#126191
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.