Revert to the old(2026.19) UI

[gavinjeremiah]

The new UI requires information from the branch/history UI as well as the changes UI in order to understand where you are at and the meaning of the current change set.

The old UI had no issues and communicated the information is a surprisingly concise and usable format. The new UI feels like a regression due to this.

[love-linger]

All the information of current branch including tracking status has been displayed in the right side of the tool bar. For other information in old UI, you still need to switch to the HISTORY page. What’s the missing part you want to get?

[gadfly3173]

What’s the missing part you want to get

For example, in the old UI, when checking local changes, you could directly switch branches, view the branch list, Fast-forward, etc.; now you have to click the Dashboard button one extra time to do so.

[love-linger]

If it's this kind of scene, I don't think it's a regression. Now it's just that the functions of each page are clarified. And when users process local changes or stashes, there is more space for diff, which makes the work more focused. 在 2026年9月16日，09:45，Gadfly ***@***.***> 写道：  [https://avatars.githubusercontent.com/u/28685179?s=20&v=4]gadfly3173 left a comment (sourcegit-scm/sourcegit#2714)<#2714 (comment)> What’s the missing part you want to get For example, in the old UI, when checking local changes, you could directly switch branches, view the branch list, Fast-forward, etc.; now you have to click the Dashboard button one extra time to do so. — Reply to this email directly, view it on GitHub<#2714?email_source=notifications&email_token=AA7DBGMQPSVH5ILTKVXNABD5PHWEDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRZGA3TOMRWGQ2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5690772644>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA7DBGKTZO2X2ULAEPXVLAD5PHWEDAVCNFSNUABFKJSXA33TNF2G64TZHM2DENJYGM3TCOJVHNEXG43VMU5TKNBWG4ZDOMRYHE4KC5QC>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/AA7DBGJB6Z4OSZ76OKIRPBD5PHWEDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRZGA3TOMRWGQ2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android<https://github.com/notifications/mobile/android/AA7DBGPTCELNIMLWLGKUYJL5PHWEDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNRZGA3TOMRWGQ2KM4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

[RussianRonin]

I definitely prefer the v2026.19 view. I could change branches easily and review changes without having to swap entire pages. A single pane is great. I am back on it because it is just an easier workflow. The dashboard page has WAY too much wasted space, especially on 1440p monitors.

I do see the argument of being able to view the history and local changes on the same view. But for me personally, I am either looking at local changes or history, never both at the same time.

[dwndland]

I personally like also the old screen more (Thats the reason why I made a fork where I changed just that).
I tried to get used to the new side par panel, but it was failing for me, mainly for security reasons.
For me who switches branches and projects a lot, the risk is high I do pushes on the wrong branches and recognize first if my push gets rejected. If it would be bold white on the left side, I can more easily see if I am on the right branch. I know its there on the top right, but there it can be missed more easily.

So having the branches visible all the time give me a big security (feeling) that all is fine and I can push.

Maybe we could have it as an option instead? Users with less workspaces, repositories and branches might be fine with the bar only.
(I have 7 workspaces, 3 to 10 tabs each workspace and about 4 to 7 branches on each tab which is not a workspace)

[goran-w]

FWIW, I beg to differ - I find the new UI uses screen estate better and is less cluttered.

• In the "Dashboard" (previously HISTORY) view we have the overview of all branches, remotes etc along with the log-graph.
• The "Local Changes" view is now more focused on preparing a commit (towards the current branch as indicated in top right) and has more space for diffs.
• The same goes for the "Stashes" view, which is targeting the local worktree when applying changes (possibly by creating a new local branch).
• Switching between these 3 views can be done quickly, by hotkeys Ctrl+1..3.

[dwndland]

For me, seeing the other branches and origins while I do like suash merge or rebases, gives me a more high security I target and pull the right stuff

I saw before there were commits with the sidebar but collapsible. Would that not be a compromise for all?
Keep the old merged side bar if expanded and the current one if collapsed. Then both worlds are happy :D
(Also me, if focus on commits, I could use it collapsed, but if I do branching work, rebase, sqash, fetch and so on I can expand :D)

[goran-w]

For me, seeing the other branches and origins while I do like suash merge or rebases, gives me a more high security I target and pull the right stuff

Hmm, I'm trying to understand... While you initiate a merge or rebase you WOULD be working in the Dashboard view, where you ARE still seeing the lists of branches and remotes etc, right?

It's only after the merge/rebase is already performed that you would be switching to Local Changes (if you didn't commit directly), and by then you are only preparing the commit against the target branch (as indicated in upper right corner). The source branch is no longer involved, since the merge/rebase is already performed? (And if the lists of branches and remotes etc were still shown here, how would it give you "more high security"?)

[dwndland]

Pretty much, yes.
Because on the left I see the current bolded, and the branch I come from still has the selection background color, so during the whole merge, I can see on the left where I come from and whats the target.

Seeing the branches, local and remote, all the time, is a big benefit for having always the proper overview of the daily work

[dwndland]

Random side note.
Many collegues still use SourceTree like caveman and I always try to convince them to use the way better SourceGit instead.
This is a pretty significant UX change, so for me it gets harder. They already struggle with the stage and unstage panel be swapped, with this UX change, they would totally block :D

[dwndland]

I just experimented (I still try the side bar to see if i can get used to) and that was my workflow

• I was on the Dashboard and fetched all
• I saw one of my branch need an merge, and did that
• Got a conflict, switched to local changed, solved it
• switched back and fetched again to see if I need to merge again
• switched back and committed after looking on the top right if I am on the right target
• switched back to dashboard to see if all is right and pressed push on remote

On the old screen it would have been

• fetched all
• saw one of my branches need a merge, do that
• Got a conflict, solved
• click on fetch again
• see no another merge needed
• comitted
• pushed

no need to do any switch, since I do not need the history at all, I just need the branches in this scenario.

[goran-w]

on the left I see the current bolded

That's the same branch that's shown in the upper right corner, though. (NOTE: You can navigate to HEAD from there, as well.)

the branch I come from still has the selection background color

That's a slightly risky assumption, though! If you would for once divert from that exact workflow and instead initiate a merge / rebase from the context-menu of another selected commit within the log-graph, then the selection background in the sidebar list could be very misleading (if you assume it's still your source branch)...

[goran-w]

I saw before there were commits with the sidebar but collapsible. Would that not be a compromise for all?
Keep the old merged side bar if expanded and the current one if collapsed. Then both worlds are happy :D

@love-linger Any comment on this?

[dwndland]

That's a slightly risky assumption, though! If you would for once divert from that exact workflow and instead initiate a merge / rebase from the context-menu of another selected commit within the log-graph, then the selection background in the sidebar list could be very misleading (if you assume it's still your source branch)...

I know what you mean, but after month, I never was run into any issue.
The thing on the end is, I feel way more save what what I am doing if I can see all the branches all the time, especially since I have always so many branches and repositories open at the same time and work in parallel with it.

Its fine if you want to defend the UX decision, I an also life with my fork. Other than that SourceGit is the perfect tool for me. And if I look on the origin of this ticket, we are at last three people unhappy with that, and I might be only the loudest at the moment while the other wait of the outcome here :D

[gavinjeremiah]

I just experimented (I still try the side bar to see if i can get used to) and that was my workflow

* I was on the Dashboard and fetched all

* I saw one of my branch need an merge, and did that

* Got a conflict, switched to local changed, solved it

* switched back and fetched again to see if I need to merge again

* switched back and committed after looking on the top right if I am on the right target

* switched back to dashboard to see if all is right and pressed push on remote

On the old screen it would have been

* fetched all

* saw one of my branches need a merge, do that

* Got a conflict, solved

* click on fetch again

* see no another merge needed

* comitted

* pushed

no need to do any switch, since I do not need the history at all, I just need the branches in this scenario.

This is what I would prefer to avoid. The amount of clicks to get work done and understand where I'm at has increased. I would prefer to have the old UI, where a single glance and 1 or 2 clicks would reveal everything I need to know, vs having to stitch together information across two different windows.

A compromise would be to move the branch name closer to where the eyes rest after moving to the changes page. Like the top left of the screen.

I understand if this is not done, but I wanted to voice my opinion in case others felt the same.