The header thing must be a bug, I can't imagine that won't get fixed.
Ask HN: Thoughts on new GitHub layout?
181–190 of 590 posts
Re: Ask HN: Thoughts on new GitHub layout?
#182Re: Ask HN: Thoughts on new GitHub layout?
#183I 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. 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…
For us, if the status is red in master, it doesn't mean the code is wrong, it means something went wrong in the deploy pipeline.
Re: Ask HN: Thoughts on new GitHub layout?
#184Re: Ask HN: Thoughts on new GitHub layout?
#185Earlier quoted context omitted.
> I guess people with huge displays don't mind... I use a ultra-wide (2560x1080) monitor and it looks terrible [1]. The repository header being "fluid" put the repository name and watch/star/fork buttons so far out of the rest of the repository info, like branch name, commit info etc., that using GitHub maximized feels very weird and tiring. I get using the whole resolution for the menu bar, since its content is disc…
The fluid width makes text harder to read. There's a reason why newspapers print in skinny columns. I wish they would at least let me set a max-width on the body.
Re: Ask HN: Thoughts on new GitHub layout?
#186I 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…
Re: Ask HN: Thoughts on new GitHub layout?
#187The metadata is placed to the right as it should have always been. The languages are in the sidebar and are visible without me remembering that typescript is somewhat dark blue.
Also the new look is more modern and unlike most people here I am not afraid of change.
Re: Ask HN: Thoughts on new GitHub layout?
#188Not a fan of the new rounded corners on everything. Also, don't like how a repository's navigation is no longer aligned with the content of the repository itself. Just seems off. Other than those two, everything else seems OK.
Re: Ask HN: Thoughts on new GitHub layout?
#189Earlier 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…
It's not so clear cut. Most places I've worked, we don't build artifacts (docker images, whatever) until there's a merge to master or a tag has been pushed. This automatically means that even though your tests remain green, you still want the status check for the stuff that isn't relevant inside a PR. For us, if the status is red in master, it doesn't mean the code is wrong, it means something went wrong in the deplo…
The projects I've worked on have used a bot for merges, and that bot handles building artifacts. In some cases, there's a lighter CI for "this looks reasonable", and then the full CI (including building artifacts and running more extensive test suites on every supported platform) runs before merging.