Repository navigation
It still miss some Git Tree renrender #266
Description
I did a big job of fixing the git tree to make it rerender after actions.
Still looks like there is few missing. (Seems rare and happens after a weird rebase that i've done where i was on the main with few commits not pushed then create a new branch and push commits on that branch instead and reset the main on origin/main.. well you can see how edge case it was.
At the end it only seems to be a miss rerender of the git tree.
But when i close and open back the app, it looks good!
Activity
t1gu1 commentedon Oct 13, 2026
I find another example where when i am checking out a previous branch the new branch with a pushed commit was disappearing.
The new branch is base on the previous branch i checkout (If that matter)
Again, if i close the app and open it back, all is good and my new branch is present.
At first, i was scare that it deleted my branch.
t1gu1 commentedon Oct 13, 2026
Oh well, that case still happens.
Like the commit is from the other branch.
But since, i reset main on that commit. So it should now be part of main and not the other branch.
devlint commentedon Oct 14, 2026
@t1gu1 thanks for the detailed report — the cause was two caches keyed only on the newest commit, so a ref move that keeps the top commit (reset main onto origin/main, a branch on an existing commit, checking out a previous branch) was invisible until restart. Details in #267.
Could you try the
fix/git-tree-stale-after-ref-movesbranch and replay the scenarios you hit? If you have a large repo at hand (5000+ commits), a quick feel of whether the graph stays responsive after checkouts/resets would also help: every ref change now forces a reload.docs(changelog): Git Tree follows ref moves (#266, #267)
fix(desktop): Git Tree follows ref moves that keep the top commit (#266…