Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Thoughts on new GitHub layout?

news.ycombinator.com

Post reply on HN
Print view View original

281–290 of 590 posts

Re: Ask HN: Thoughts on new GitHub layout?

#282

Post by yellowapple »

lukeplato wrote: post #249
ljm wrote: post #126

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…

> the single worst change is that you can't see the latest commit status from the repo screen Maybe they are trying to push towards using badges/shields inside the README [1]. But yeah, I agree that this makes monitoring repo health less convenient. [1] https://shields.io/category/build

> Maybe they are trying to push towards using badges/shields inside the README

If they're pushing for that, then keeping the README below the file list seems counterproductive.

Re: Ask HN: Thoughts on new GitHub layout?

#283

Post by prputnam »

In a quick browse of the thread I didn't see this mentioned yet - it seems to have broken multi-line suggestions which I thought was a great addition.

I do wish there was an option to use more screen-width, and this does seem to be a step in that direction.

Re: Ask HN: Thoughts on new GitHub layout?

#284

Post by natfriedman »

ljm wrote: post #126

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.

Re: Ask HN: Thoughts on new GitHub layout?

#286

Post by chrisandchips »

natfriedman wrote: post #284
ljm wrote: post #126

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's great to read this comment - it's always nice to know that community suggestions aren't just cast into the void

Re: Ask HN: Thoughts on new GitHub layout?

#287

Post by GuiA »

bE9a3S5So8igd3 wrote: post #258

The worst redesign yet. It looks even worse than an early version of Gogs I tried. Of course, if you're paying designers they ultimately have to design something even if it's crap. Ideal github design was maybe in 2012. Unrelated to the redesign, but the documentation for things like Actions just scream "microsoft." It was really hard for me to find the important information; had to sift through pages of abstraction…

Sorry tangential, but what's this frog neural network project? Looks fun!

Re: Ask HN: Thoughts on new GitHub layout?

#288

Post by rwoll »

yellowapple wrote: post #282
lukeplato wrote: post #249

Earlier quoted context omitted.

> the single worst change is that you can't see the latest commit status from the repo screen Maybe they are trying to push towards using badges/shields inside the README [1]. But yeah, I agree that this makes monitoring repo health less convenient. [1] https://shields.io/category/build

> Maybe they are trying to push towards using badges/shields inside the README If they're pushing for that, then keeping the README below the file list seems counterproductive.

I’d second this. In fact, I think the README should be the first thing (potentially in collapsible form so you can easily see the file list without scrolling too much).

Intuitively, I’d bet most people landing on the front page of a repo are consumers of the library looking for a README with info on how to get started or where to look for information on how to get started. Again, this is only intuition—no data to back it up. Project maintainers are most likely interacting with the issues and PR sections or code on the command line.

Re: Ask HN: Thoughts on new GitHub layout?

#289

Post by nimih »

bconnorwhite wrote: post #234

This is the MacOS 11 thread all over again. Apparently no one on HN has been through a redesign... For those of you complaining, congratulations, you've discovered ~ nostalgia ~ In two weeks you'll inevitably find the old design ugly, and forget GitHub ever looked any other way. In 5 years, each will get another round of improved designs, and there will be a thread on HN full of people complaining about how the new d…

> If you really don't like the rounded borders, use wget

Or just add

    * {
      border-radius 0 !important;
    }
to the page stylesheet, either via userContent.css or a browser extension. Once you know the process, it's extremely easy to hack around web developers' poor decisions if you know a bit of CSS yourself.
Post reply on HN