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

551–560 of 590 posts

Re: Ask HN: Thoughts on new GitHub layout?

#553

Post by JoshTriplett »

meddlepal wrote: post #341
JoshTriplett wrote: post #178

Earlier quoted context omitted.

> 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. Omitting the commit message is a net improvement to me; I've found that the commit message of the random commit that happens to be at top of tree is completely unhelpful for someone browsing the rep…

> If it hasn't passed CI and status checks, it shouldn't be in your default branch. Broken master is inevitable in a large enough project. Really what you want is to be able quickly fix a broken master. By all means keep a perfect master if you have a toy project but once things have several developers hacking on a project with multiple artifacts and hundreds of thousands or millions of lines of code then you need to…

> once things have several developers hacking on a project with multiple artifacts and hundreds of thousands or millions of lines of code

That's exactly the case where you need more strictness about passing tests and CI before getting merged.

It amazes me when I come across a major project where the latest committed version often doesn't even build, let alone pass tests.

Yes, there are absolutely cases where you can't test everything; for instance, if you have complex combinatorial configurations and one obscure configuration fails. But that's a far cry from "inevitable in a large enough project". On the contrary, it's more important to avoid in a larger project.

Re: Ask HN: Thoughts on new GitHub layout?

#555

Post by ian0 »

Hedja wrote: post #117

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…

I think they designed it using regular sized screens, works fine on my 13'' laptop.

Honestly - pretty refreshing, designers typically forget to test on low end monitors - not high end ones!

Re: Ask HN: Thoughts on new GitHub layout?

#556

Post by t0astbread »

lostmsu wrote: post #314
t0astbread wrote: post #131

Earlier quoted context omitted.

Really? I found that I only really look at the code when I look at projects I'm involved in. Usually though I use GitHub for discovery and then I care much more about the languages, commits, releases and Readme.

To be fair, that means you are not the one paying their bills.

Fair point. Although I do wonder how enterprises manage their dependencies. Do they not use GitHub like that at all?

Re: Ask HN: Thoughts on new GitHub layout?

#558

Post by duhi88 »

DreamScatter wrote: post #153
duhi88 wrote: post #146

Earlier quoted context omitted.

I wouldn't consider any of your criticisms as being "less accessible". To take your example of the languages, the new design is more accessible. It has a clearly labeled heading, and I can see the names of the languages are being used without clicking on the bar. The old design has no hints that the striped bar (or in the case of `linux`, grey) is supposed to be informative. We're all just used to clicking that bar i…

They could have left the languages in the same place where it was before. Now it requires extra input and mental effort to find the languages section. This is definitely a step backwards. Not complaining about the design of the new languages section, but the layout is just completely terrible and useless.

I have to disagree with you there. Previously, I had to click on the tiny strip before I could see the languages. Now it is available right away.

For a new visitor, this is infinitely better because it is clearly labeled. For returning users, the only hurdle is getting used to the new location (which is made easy by the clear heading).

You could argue that project languages are more important than the contributors and should be placed above that content. Regardless, it is clearly a step forward.

Post reply on HN