301–310 of 590 posts
I also like that it's a lot friendlier to narrow windows (no horizontal overflow/scrolling); makes it more convenient to put it side-by-side with something else.
I am not affiliated with Source Hut in anyway other than being a satisfied customer.
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.
It's great to read this comment - it's always nice to know that community suggestions aren't just cast into the void
main repository view on widescreen puts all the "Code, Issues, Pull Requests etc..." buttons way over to the left. Why not just centre it like the repository files view below it? Seems completely bizarre and adds extra mouse movement between files and the buttons above.
Earlier quoted context omitted.
> 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 bac…
If I want to read your readme ill click on your readme. If im visiting your github page I want to read your code.
Eee, theyre downplaying the focus on cross platform friendly md files showing repo info, instead they want you to use the newly more prominent side bar that is wholy only available on github.
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 don't expect companies to take on my feedback. I do expect them not to treat it like it's a joke.
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…
I find it much more difficult now to line up filename and last modified time in the file browser. And I agree on the low density. Plus it now looks like a children's toy, not like a work tool. A while ago, there was an article on HN about kawaii cuteness culture sneaking into everything. It appears that has happened here.
Like many others, I use Github every day. Changes like this add friction to our workflow. There better be a damn good reason for these changes, otherwise it's a pointless redesign that looks no better than it did previously while simultaneously adding a slight overhead as users "learn" the new layout. Does anyone know of an option to revert this update?
My hypothesis is the point is to compete with Jira. That would be MS's biggest competitor in this space, and the changes make it look a whole lot more like that. I wonder if MS has gone back on their word to leave GitHub to it's own devices...? I have been unable to find a method to revert. Best option might be to make a bunch of noise. Other than that, it's migration time.