Avoid loading all worktrees

[svartkanin]

I have some repositories that have dozens of worktrees collected over time. Is there a way to avoid loading them all as windows when adding the repo to the paths via the config?

[junglerobba]

I think this PR seems like something that would address your issue, if I'm understanding correctly. Would require some rebasing work after some of the changes we've had lately though.

[svartkanin]

I think that would kind of address it. Although it sounds like that if I wanted to work on 2 worktrees simultaneously then that would open 2 different sessions? Not sure that's a very useful behaviour as having a single session with both as windows sounds like a better approach.

[junglerobba]

Although it sounds like that if I wanted to work on 2 worktrees simultaneously then that would open 2 different sessions?

Yes, in that case each worktree would be shown and openable as a separate session.

Hm, I'm not quite sure what the optimal way of handling this is from either configuration of UI-side. Either we'd need per-repo configuration to blacklist worktrees or add an additional worktree picker (with multi-select???) for repos with multiple worktrees. Not sure what would be the way to go here. I can't really speak on this very well either because I don't really tend to use worktrees all that much.

[svartkanin]

Yes that gets complicated quickly.
Would it be possible to have an option to specify the max number of worktrees and then use the n latest added ones when loading the repo?