.repository-content > .d-flex { flex-direction: column !important; } .repository-content > .d-flex > * { width: 100% !important; padding-left: 0 !important; padding-right: 0 !important; } .repository-content > .d-flex > :last-child { margin-top: 2rem !important; } .Box-row:not(:last-child) { border-bottom: 1px solid #e1e4e8 !important; }
Ask HN: Thoughts on new GitHub layout?
571–580 of 590 posts
Re: Ask HN: Thoughts on new GitHub layout?
#572A related question: Why is it so hard to find a most up-to-date fork? When I come upon a useful lib, there would often be hundreds of forks. 99% of those forks don't make any commit on top of upstream repo. Why even bother forking if you're not actually changing the code? Can we agree those are useless and just hide them in GitHub interface? You can list all the forks on GitHub, there's even a nice hierarchy, but no…
Re: Ask HN: Thoughts on new GitHub layout?
#573I submitted feedback over it but, aside from the over-reliance on rounded corners, and making pills and buttons hard to separate, the single worst change is that you can't see the latest commit status from the repo screen. Instead, you get the commit hash, and have to click a tiny ellipsis button to get the commit message and the status indicator. When I'm browsing on github and not using git directly, the commit sho…
Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.
If there isn't you've done a tremendously bad execution job and no testing.
Re: Ask HN: Thoughts on new GitHub layout?
#574Earlier quoted context omitted.
I have a light sensitivity condition; large patches of white really hurt to look at for any real amount of time. Please consider implementing an optional dark variant in the vein of https://github.com/StylishThemes/GitHub-Dark as an option.
It's coming.
Re: Ask HN: Thoughts on new GitHub layout?
#5751. Not being able to click to a repo home page if you are on a nested page, or link to a file from the web etc.
2. Markdown files displaying in raw form when someone links to a ReadMe.md file directly etc.
Re: Ask HN: Thoughts on new GitHub layout?
#576Earlier quoted context omitted.
Tangential comment: I just opened the link with the new design on my phone and it was a delight to look at compared to whatever I saw last time. I think the design changes were made keeping in mind smaller screens, which might be what the user data suggested (how am I to know). But I agree with other comments that the top bar content could be aligned with the rest of the content. Stretching it to each end is causing…
Surprisingly, most of us don't edit code on our phones.
Re: Ask HN: Thoughts on new GitHub layout?
#577I submitted feedback over it but, aside from the over-reliance on rounded corners, and making pills and buttons hard to separate, the single worst change is that you can't see the latest commit status from the repo screen. Instead, you get the commit hash, and have to click a tiny ellipsis button to get the commit message and the status indicator. When I'm browsing on github and not using git directly, the commit sho…
Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.
Re: Ask HN: Thoughts on new GitHub layout?
#578I have a single major problem with all of their new layouts. They place content at extreme ends of the screen, completely stretched out like a rubber band with No Man's Land in the middle. In this case, the top half is stretched and the bottom half is centred. Completely inconsistent and tiring for your eyes darting around corners of the screen. Example: https://twitter.com/JahedDEV/status/1275532988772683776 I don't…
Just logged into GitHub, freaked out when I saw the redesign, and came straight here to say exactly this. It's unnatural eye movement to look wide for platform navigation, then narrow for README/repository navigation. This is outright bad design. There was nothing wrong with GitHub's UI before, it was probably the closest thing to "perfect" I'd ever encountered. Alongside that incredibly irritating "navigate to code…
It seems to me Github from the Microsoft acquisition is going into a wrong direction.
Re: Ask HN: Thoughts on new GitHub layout?
#579Earlier quoted context omitted.
Thanks for the feedback about the latest commit status. This is something we should definitely fix. Also – I don't think there is a principle of lowering information density at work here. I think it's just a design that we will keep iterating. We are pro information density at GitHub.
FWIW, on a 1440p monitor, there's a huge amount of wasted/empty space, which means that the things that the space is used for should be pretty critical or it seems like a colossal waste overall. Here's my input. Maybe it's useful? I don't know. https://imgur.com/a/S9YRBq0
Re: Ask HN: Thoughts on new GitHub layout?
#580Earlier quoted context omitted.
Also there's font-size party happening on the home's right sidebar. 16px, 14px, 12px in a rapid succession. Meanwhile, on Pull Requests' right side bar everything is rendered in 12px size. Just to be clear, 12px is equivalent of 9pt. That's fairly small on screen. For comparison the README body text is rendered in 16px, which is equivalent of 12pt. By the way, HN body text is 13.33px, about 10pt.
Weird design choices like this are why I've been setting minimum font sizes in my browser since the day the feature was added. It's a life saver, especially on high-resolution displays.