Handling a large number of applied branches

[rhizoome]

Version: 0.14.20 v3 OS: Linux (built from source)

I have a lot of applied branches. I work on a project with countless independent parts (ports of a Linux distribution*) and the review process takes ages. So I need to use the Branches view, because it is searchable, in the current version of Workspace view I'd never find the branches I need. (If I select an applied branch in the Branches view, it says Apply to workspace, which is wrong. It should be Unapply stack.)

Generally I wish for one of the following:

• That I could jump to the correct branch in Workspace view from the Branches view
• Or that the list below in Workspace was searchable / filterable and the branches were collapsible

EDIT: In v2 I collapsed and sorted the branches (active/inactive), there was a lot of tilting my head involved, but combined with sorting the branches, it was working okeyish.

_ * only independent on source level, since the packages depend on each other, it is best to have all the lastest updates applied

[Byron]

Thanks so much for sharing!

I see how finding/going to the right branch can be cumbersome, and that searching for them seems most natural especially given that such a feature already exists in the "Branches" view. From that point of view, it seems intuitive to have a way to "jump" to applied branches.

The issue with applied branches allowing to be applied again is known but apparently not tracked separately.

Let me CC @PavelLaptev for the UX aspect of this issue, and @krlvi just for the heads-up.

[rhizoome]

@Byron Am I missing something or got the problem worse with 0.14.34? No complaint, I know the GUI is not finished yet and my use-case is rare. I still think a filter would work, but since this seems a bit of a revert to the old GUI style, we might go back to collapsing and manual sorting?

[Byron]

There has been a lot of [feedback (Discord)] about workflow issues with the current iteration of the user interface, and it's definitely being worked on to get back to that sweet-spot, and to hopefully work better than ever before. You are very welcome to share your pain-points or maybe even the things that work well to help keeping them around. Thank again.

[rhizoome]

I am disciplined naming my branches, so a filter hiding all stacks that do not match the filtered stack name would help:

• I could type "maint" to get all the long-term maintenance branches
• I could type "update" to get all the package upates
• The branch-name contains the package name so I can also search that

There are probably better solution, UX is not something I often do. But that is basically the use-case.

An example, I added a search-box in the right top corner:

[Byron]

Thanks a lot for sharing! In case it's not on any list yet, CC @PavelLaptev.