For example at some point you developed component and it was committed. Then something happened and it was removed (architecture changed, reworked code, etc.). It would be nice to still be able to search for those files or display them as separate list.

It would be great if ReviewBoard could be supported natively for pre-commit reviews.

It's possible to call RBTools via an external tool call but it doesn't work for SVN repositories because they aren't standard git-svn repositories and aren't supported by RBTools.

It would also be handy to have UI support for creating and updating ReviewBoard reviews.

Now there are two built in layouts (Main and Review). I would like to be able to customize some of custom layouts and switch between them.

To stay focussed on the current repository only.

Do you have support for Jujutsu on your roadmap? We have developers using Jujutsu and I'm also tempted to use it because it has some really nice features. Stacked PRs and the option to resolve merge conflicts later would be the two features I'm most interested in.

BR

Martin

When merging a branch which leads to conflicts, I often run into the problem that the conflicted files are spread across hundreds of rows in the Files view:

It is not practical at all to scroll though hundreds of files just to find the 5 conflicted files you need to resolve manually. The only practical option seems to be to sort the list by the State column, to have all conflicted files at the top.

That works fine, but after the merging state is left, the new sort order remains, and I have to change the sort order again to get the list sorted by relative directory & file name (i.e. a sorting order which feels comfortable for me).

As this is happening regularly, I'm constantly changing the sort order, which is annoying. I wish the sort order in the merging state is memorized separately from the sort order of the normal state. So every time I run into the merging state, files will be sorted by State automatically, and after leaving the merging state, sorting automatically changes back to Relative Directory & File Name (i.e. the sort order of *before* the merging state).

This would be a big quality of life improvement :-)

I often select to commits to see the differences between them. It would be great to have the path/commits between the selected highlighted.

Currently, the repositories can be grouped under custom groups, much like placing files into separate folders.

I would like to propose that you implement the same feature for local branches. Another variant could be to allow the tagging of branches. I don't mean the git tagging, I mean assigning custom labels to a branch and the providing a quick way to filter the branches by one or more selected tags. Either way works for me, but probably I would prefer the folder approach.

The reason for this is that I have lots of local branches that correspond to issues I've been working on throughout time. It becomes harder to figure out where some branches are at, especially when I have to switch context. I would like to
create a group called "Done" or "Implemented" and move the branches to this group after they are done to get rid of the visual clutter.

There were some previous suggestions on these lines under Branches view, though they are not exactly the same as my request.

When I open Conflict Solver, in numerous cases it overwhelms me with lots of unrelated changes because files were changed a lot. There may be only a few lines actually changed in the commit, but I see so many colorful lines showing the differences between ours/theirs and the merge result that it's difficult to understand what's going on without looking at the original commit. It's a confusing experience.

It would be great if all changes not relevant to the applied commit (as a result of cherry-picking, rebase, etc.) were somehow (optionally) highlighted. For example, irrelevant changes might be in muted colors.