You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the Git Web UI to pull down changes to a branch (checked out main, synced remote branches, merged origin/main into main). The resulting merge commit contained 7 new and 1 changed files (git output was 18 lines total), plus the corresponding "Input" actions logging which had 24 lines (for a total of 42 lines of output). There were new-lines within the text, but all of these were mashed together into a single line in the HTML view (because HTML does not recognize line breaks on their own)
This makes the output log extremely difficult for a human to visually skim. (My browser was maximized and the alert message box took up about 30%-40% of the vertical screen height.) In my experience, pulling down commit histories containing 3+ files is the norm.
A quick solution would be to place all this text inside a <pre></pre> element and give it a reasonable max-height (say 200-ish px) so large pulls/merges do not cause the alert notification region to completely overtake the view screen. A better solution is probably to actually parse lines into an HTML equivalent (<br>, <div>, or <p>) so you get text wrapping too.
The text was updated successfully, but these errors were encountered:
cambot
changed the title
Git Web UI: Merge output is unreadable
Git Web UI: Merge output quickly becomes unreadable
Apr 29, 2025
Uh oh!
There was an error while loading. Please reload this page.
I used the Git Web UI to pull down changes to a branch (checked out
main
, synced remote branches, mergedorigin/main
intomain
). The resulting merge commit contained 7 new and 1 changed files (git output was 18 lines total), plus the corresponding "Input" actions logging which had 24 lines (for a total of 42 lines of output). There were new-lines within the text, but all of these were mashed together into a single line in the HTML view (because HTML does not recognize line breaks on their own)This makes the output log extremely difficult for a human to visually skim. (My browser was maximized and the alert message box took up about 30%-40% of the vertical screen height.) In my experience, pulling down commit histories containing 3+ files is the norm.
A quick solution would be to place all this text inside a
<pre></pre>
element and give it a reasonablemax-height
(say 200-ish px) so large pulls/merges do not cause the alert notification region to completely overtake the view screen. A better solution is probably to actually parse lines into an HTML equivalent (<br>
,<div>
, or<p>
) so you get text wrapping too.The text was updated successfully, but these errors were encountered: