Manually (re)ordering the branches list

[pavleprica]

Hey team,
This might be an odd request, I'm not sure if I'm the only one having this OCD.

But when working on a bigger feature, that will consist of multiple PRs, I tend to branch a lot. (You don't say, I know I know)
But also, it would happen that I jump to a whole other context and different feature, that also might have multiple branches. Even if its a single branch bugfix.
It ends up in a not sorted list of branches in a way.

For example, I have branch-1, branch-2, branch-3. But then I start jumping around, just checking them out. Maybe to just sync with the base branch. And it ends up in branch-3, branch-1, branch-2. No biggie I know. Solvable by just checking them out in the correct order.

Why I like having them sorted? So I don't mix up by accident on where I have left off. Sometimes they can have a bit of similar names.

So, the proposal is, if possible to manually sort them? Literally moving arrow-up/down and ordering them in the desired order.

If this makes sense at all, I can also try to take it up myself.

[stefanhaller]

Solvable by just checking them out in the correct order.

From this, I suspect that you have your branches sorted by recency, which (unfortunately, if you ask me) is still the default. I recommend sorting branches by committer date, which in many cases works better for me. It won't necessarily solve your problem though -- just mentioning it anyway.

One way to solve it could be to sort alphabetically, and then use a naming scheme that gives you the order you want; e.g. 01-preparations, 02-backend, 03-frontend.

[pavleprica]

From this, I suspect that you have your branches sorted by recency, which (unfortunately, if you ask me) is still the default. I recommend sorting branches by committer date, which in many cases works better for me. It won't necessarily solve your problem though -- just mentioning it anyway.

Legit option. I mean, in a way, solvable by a workaround.

One way to solve it could be to sort alphabetically, and then use a naming scheme that gives you the order you want; e.g. 01-preparations, 02-backend, 03-frontend.

Though of that too. Though, would clash with the company/team naming policy. And I guess I'm lazy (hehe get it, lazy git :D (I'll show myself out)) to have different origin/local naming