521–530 of 590 posts
Earlier quoted context omitted.
Also you used to be able to hover over a commit and see the full commit message. That doesn't seem to work anymore. Overall, seems like change for the sake of change. Boo.
That absolutely does still work. Used it a few times today.
Earlier quoted context omitted.
Don't forget: * Added dark mode
I think dark mode was a harbinger of dumbed down UI. Instead of spending time on one good UI, designers and developers were forced to make 2 mediocre ones instead. Plus dark mode is easier if you remove all detail and depth from control elements.
I 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.
I'm sure as I get use to the new design I'll be able to navigate without much issue, but still figured it's good to share with ya.
Thanks for gathering feedback!
Earlier quoted context omitted.
Let's take the simplest action - cloning a repo. Old: https://web.archive.org/web/20200619163555/https://github.co... New: https://github.com/torvalds/linux It was always strange to have all the language info at the top
It was in a location where it didn't take up any space. Now it's consuming a massive amount of space.
I don't mind the aesthetic design changes but the layout drives me crazy. I count 4 separate alignments in the new repo page on my 15" macbook's full width browser window! I found and modified a Firefox user style to fix the alignment for wide windows. Original mozilla userstyle: https://gist.github.com/healingbrew/acc65ad439379eabdbb276e8... Modified stylish chrome extenstion userstyle: https://gist.github.com/monta…
1.) Everything feels left especially on my 21:9 display. This makes going from opening issues to clicking "Code" a very long mouse movement.
2.) There aren't grid lines on the file view.
3.) It looks unprofessional. Professional tools have this feel to them, and this new theme doesn't have it. It feels like a toy that shouldn't be in the toolbox.
At this point I may just move to GitLab. It seems more feature packed and you can have it mirror a repo to GitHub for the users don't want to make the switch.
Earlier quoted context omitted.
Wow, that's pretty bad. Logical consistency was clearly not a guiding principle of this redesign.
There is a consistent principle behind those choices: rectangles with slightly rounded corners are clickable, while rectangles with semicircular sides (“pills”) are not clickable. It's confusing because I've never seen another site that distinguishes clickable elements in that way, but I can imagine we'll grow to find it intuitive with enough usage.
But a good UI should be intuitive for a first time user. This seems objectively worse.
I 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…
Ya, I didn't understand this design choice. For a while I've had some custom css which also extends the width of the main content on github as well because I've always found reading some github issues with logs in them challenging. This is the css I'm running now to fix this, as well as extend the width of the main content. The 1600px is such that when using i3 and having my browser be half the screen it consumes mos…
.col-md-9 {
width: 100%;
margin-top: 1em;
}
.col-md-3 {
width: 100% !important;
margin-bottom: 1em;
}
.flex-md-row {
flex-direction: column!important;
}
.flex-md-row {
flex-direction: column-reverse!important;
}
.BorderGrid--spacious .BorderGrid-cell {
padding-top: .2em;
padding-bottom: .2em;
}
div.BorderGrid.BorderGrid--spacious > div:not(:first-child) {
display: none;
}I 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.
It'd also be nice if you could have the bar at the side up top, or shrink it a lot. It takes up a quarter of the screen space plus padding and margin. For reading README.md files and Awesome Lists, it's extremely intrusive.
Alternatively, you could have the README.md below the longer element of the new "sidebar" and the file list, so that it can take up the whole width of the screen.
I hope you read this!
Earlier 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.
I just want to echo what others are saying about the sidebar on the right. It feels like it's taking up way too much real estate without offering much value. The most important information feels constricted to me. I'm sure as I get use to the new design I'll be able to navigate without much issue, but still figured it's good to share with ya. Thanks for gathering feedback!
Nat drive-by commented on a non critical comment. Did not address our main concerns. Did not say anything like "let us take all this in and come back with something articulate" either...
Definitely feel like Nat and GitHub are actively ignoring is at this point