You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing the following issue (VS Code extension 0.1.70 + Sapling 0.2.20241203-120811+a2174689):
Repo is local-only, I have two branches (A and B), the latest commit is in A.
goto A results in B not visible at all in ISL;
goto B results in both branches visible in ISL.
I have no idea what's the difference between branches in ISL's opinion and why it behaves like this. None of the commits in either branch are hidden, explicit unhide of the terminal commit in B does not change anything.
AI, when asked, seems to think that Sapling ISL by design hides branches based on some obscure logic and also AI believes this is not controllable from a config. I've done quite a thorough documentation search, I cannot find anything supporting or refuting the above.
I wonder if it's possible to change this behaviour to "show all branches" or to show everything unless explicitly marked "do not show"? It would be highly helpful.
I need to quickly goto between branches on routine basis. Current workaround is to bookmark everything, but "sl bookmark" does not display bookmarks as a tree but rather as a list, hence navigation with large number of bookmarks is a pain. Navigation through sl smartlog --rev "all()" is even more of a pain (imagine how much hassle it is to find the right terminal commit in the right branch among 1000s of commits if you don't remember what was the commit message but can only try to figure this out looking at the last several commits in the branch).
Btw, a fresh commit to B makes both branches visible even after goto A. If it's "max branch age to show" or sth like that hardcoded somewhere, would be great to be able to change it via config. Otherwise "surprise, good luck finding your work from several months ago".
Was trivial to have AI agent code a vscode extension to manage repos without any issues, so no longer need help with this. Still, would be great if official ISL had some kind of fix for this.
Activity
vdemichev commentedon Feb 9, 2026
Btw, a fresh commit to B makes both branches visible even after goto A. If it's "max branch age to show" or sth like that hardcoded somewhere, would be great to be able to change it via config. Otherwise "surprise, good luck finding your work from several months ago".
vdemichev commentedon Feb 10, 2026
Was trivial to have AI agent code a vscode extension to manage repos without any issues, so no longer need help with this. Still, would be great if official ISL had some kind of fix for this.