9 ms·
A new look for repositories
- Killswitch 11y agoSays it's opt in for the next two weeks, but I'm not seeing how to opt in.
- Mithaldu 11y agoDon't see it either. Maybe badly worded.
- Killswitch 11y ago@mdo said they're slowly rolling it out, and when it's available then you'll be prompted on the repo you own.
- jtokoph 11y agoThat's an interesting choice of rollout if you enable it for all users that see your repository instead of enabling the view for yourself for all repositories that you browse.
- hamandcheese 11y agoI would imagine that it is easier on Githubs end to configure a repo to render one way or another rather than to conditionally render it based on the current user.
- jtokoph 11y agoI guess they are slowly letting users opt in. Seems incredibly weird and slow considering the public featured announcement on the blog.
- swang 11y agoIt says over the course of the next two weeks, you'll be able to opt-in so its being slowly rolled out.
- mkelley82 11y agoI just got a notification/alert at the top of the site saying something to the effect of "would you like to try out our new layout?" yes please. voila.
- talmand 11y agoIt was there for me, just a prompt at the top with a short message and a green button. A quick reload later and there it is. Staggered roll out I suppose.
- MasterScrat 11y agoI was almost expecting them to let us add a header image to our repos, the way Facebook Google+ and Twitter do.
- themodelplumber 11y agoI would like that. For comparing many software projects I sometimes use "how complete is the Twitter profile" as a metric, just like a lot of people use "how does the website look". One software project that I've been involved with for over a decade still uses the same old stale graphics, and it's basically telegraphing the fact that the SABDFL is not big on letting other people contribute to areas he's not comfortable with.
- archimedespi 11y agoHa, they're going back to the way repo tab navigation used to work a long time ago, with the tabs on the top, like [1] and [2]. Arguably it's a nicer look with some UX benefits. [1] - https://camo.githubusercontent.com/fec1c4ab93659e759682ad5dba5308430f0d07d9/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f313335342f3635313336302f35626133336266342d643437322d313165322d393439362d6134386339373361313232342e6a7067 https://camo.githubusercontent.com/fec1c4ab93659e759682ad5db... [2] - http://cdn.appappeal.com/pictures/6089/screenshot.png http://cdn.appappeal.com/pictures/6089/screenshot.png
- netnichols 11y agoIt took me ages to get used to the old new design (that dropped the tabs on top). Glad they're switching back... definitely a more intuitive structure for me.
- lucaspottersky 11y agoand then when they decide to add new Menu Items and run out of space, they will switch back to the Sidebar :D
- yeukhon 11y agoThe second picture, probably one of the earliest interfaces of GitHub (??) reminds me of Sourceforge, in fact, the horizontal navigation exists in Sourceforge. I guess keeping things more center benefits interaction.
- masonhipp 11y agoInteresting changes, seems like the trend of pulling items out of icon-based menus and into persistent nav is gaining speed. I'm not sure how I feel about the full-width pages yet.. easier to read commit messages but stylistically I did like the icon menu on the side. The narrower version also seems ever-so-slightly easier to read, but it's hard to say without trying it first. Looking forward to demoing once the roll-out starts.
- fuzionmonkey 11y agoI hope the removal of the sidebar doesn't result in wider README views. The current design has a fixed width of 790px (including 30px of padding on each side), which leads to a comfortable number of words per line. I find readability much worse when line lengths get longer. Other than that, I think the simplified navigation is a big improvement.
- kevinmgranger 11y agoIt does feel a bit wide to me, but I haven't tried it yet. Some extra margin on each side might be nice.
- pducks32 11y agoYea I was worried about the same thing, I've tried it and it's a tad different. Give a few days I think.
- m0th87 11y agoInteresting. This is closer to the older UI, before they rolled out "Repository Next" - https://github.com/blog/1529-repository-next https://github.com/blog/1529-repository-next
- r0muald 11y agoI don't get what is different in third screenshot. Otherwise, a nice incremental change.
- tomguthrie 11y agoThe sidebar with label/milestone etc is slightly larger to fill out the space from the navigation being moved up.
- rowofpixels 11y agoI think it's that the sidebar menu is not present anymore (on the right hand side). Usually in this view it is the icons only, so pretty narrow anyway.
- mbrock 11y agoI'm holding my thumbs for a GitHub with a responsive layout. The separate mobile site is pretty nice, but it lacks tons of functionality (and it's hard to access on non-mobile). Even HN is responsive these days!
- kzhahou 11y agoHa, yesterday I counted the number of words and/or links they fit onto a mobile page. Forty! The page is almost all whitespace. Sweet, margin-padding whitespace.
- kevin_thibedeau 11y agoWell, you know minimalist design is all the rage these days.
- olalonde 11y agoWill be interesting to compare the comments here with those of 2 years ago: https://news.ycombinator.com/item?id=5894438 https://news.ycombinator.com/item?id=5894438
- kibwen 11y agoAnd bookmark this current thread for when they reintroduce sidebar navigation in 2017. :)
- cpitman 11y agoI had never noticed before that GitHub "Highly Recommends" cloning via HTTPS instead of via SSH. This is the opposite of what I usually tell people to do. I do not see any reasoning anywhere, but I might have missed it. Does anyone know why you would recommend HTTPS over SSH? Is it just the complication of setting up SSH keys?
- lamby 11y ago> This is the opposite of what I usually tell people to do How come, out of interest? In terms of peformance, cloning for HTTP is fairly efficient these days although I would concede an authentication argument. (As an aside, SSH can be blocked on some corporate networks)
- shazow 11y agoI much prefer to use an ssh key for auth than copypasta'ing the same passphrase I use in my browser.
- cpitman 11y agoBecause you don't have to keep supplying credentials when using SHH keys. It's less about speed and more about reducing the friction in common operations. It's also the way I'm used to handling things with gitolite, so that might be part of it. We already usually use SSH w/ keys for server access, so uploading public keys to GitHub isn't much of an additional hurdle.
- WorldMaker 11y agoYou can setup a credential manager in git and don't have to continue supplying credentials with HTTPS repositories. For instance, I commonly use this one on Windows [1]: https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases https://github.com/Microsoft/Git-Credential-Manager-for-Wind... [1] Although currently marked as pre-release, this is a fork/successor of an earlier one that was fairly rock solid, now with a better installer. The "pre-release" tag here mostly is with respect to the new 2FA support.
- farresito 11y agoI never understood why they changed it, but I'm glad it's back.
- masklinn 11y agoThey wanted more repository content above the fold. Turns out having discoverable and clear navigation is more important since the vast majority of the content (e.g. readmes) is going to be displayed below the fold either way.
- shadeless 11y agoI wish they reverted to the old search bar, where you could chose to search globally or just the repository you're on currently: https://github.com/blog/1492-repository-search-on-all-repositories https://github.com/blog/1492-repository-search-on-all-reposi... Unless I missed something, the only way to search globally now is to go to github.com and then use the search bar.
- masklinn 11y ago> Unless I missed something, the only way to search globally now is to go to github.com and then use the search bar. You can delete the default "this repository" facet. Just hit backspace when you're in the "local" search: http://giphy.com/gifs/l41lJC4ZrO3sEFuNO http://giphy.com/gifs/l41lJC4ZrO3sEFuNO
- shadeless 11y agoNice, thanks for the demo! I take back what I said, this is better than the old version with the dropdown.
- hultner 11y agoWow I totally missed that, I wouldn't say that it's very good UX considering that it doesn't intuitive for many, with the dropdown it's obvious that you can switch.
- masklinn 11y agoIt definitely has terrible discoverability. Same as the file Find As You Type (hit `t`, type bits of a filename).
- cpitman 11y agoYeah, the only way I ever found it was because I kept accidentally doing global searches when I though I was searching a repo. Turns out I just held backspace too long while clearing out the search bar. It took me a long time to realize what was going on.
- 11y ago
- makecheck 11y agoThere's one part of the GitHub UI that I still wish they'd change: the way "contributions" are displayed. Right now, there are accounts that seem to just fork a bunch of repositories and then do nothing with the forks. This makes those people look like massive contributors to open-source because GitHub gives them a nice "Contributions" tab with a list of popular projects under it. They also get free advertising in reverse because they automatically appear as a "Member" of the parent project's network, despite having done nothing at all in the project! At the very least, GitHub should require the forking person to have made some pull request that was accepted. If those forks aren't actually contributing, they shouldn't even be mentioned as a sub-network of the original (except perhaps as an option for the project maintainers to see, if they're curious where forks have occurred).
- stonesam92 11y agoYou don't become listed as a contributor by merely forking a repo, your fork is just included in the original project's "forks" count. The project is included in a user's "Repositories contributed to" area when that user creates a pull a pull request or files an issue. You are listed as a contributor on a project's page only once you have had an accepted pull request. EDIT: take one of my projects for example[0] - 152 forks recorded but only 8 people are listed as contributors. [0] https://github.com/stonesam92/ChitChat https://github.com/stonesam92/ChitChat
- makecheck 11y agoYes but if you go to "Members" you see all of them, which is confusing at best. The term makes it sound like this is a list of people who are members of your project, when they're not. And for something like the Linux kernel, it's not hard at all to find people who are about 236,000 commits behind the master. I agree that GitHub has some accurate views but they're all mixed and it's very easy for a list to look like something that it isn't.
- RyanZAG 11y agoFor anyone curious on how to get there: https://github.com/stonesam92/ChitChat/network/members https://github.com/stonesam92/ChitChat/network/members It lists all people who have forked instead of only contributors. The 'members' tab in general doesn't appear to make much sense.
- farnsworth 11y agoI don't see how to opt-in, where's the button?
- mikelyons 11y agoI don't see it either, maybe they're bucket testing, odd that they'd announce it if that's the case ...
- danieltillett 11y agoIs there a good way to 'deep' browse GitHub? I love just browsing through repos by language, but I have found that this is limited to a max of 500. Once you get to 500 there is no way to get to 501, etc.
- WorldMaker 11y agoYou can random walk the social graph as deeply as you want to: click on a contributor to a repository, then explore a repository they've also contributed to, then click on a different contributor in that repository, ad infinitum.
- danieltillett 11y agoThis does not allow you to efficiently browse by language.
- WorldMaker 11y agoDepends on the language. Some languages the core contributors are active enough across the language that you can get a very wide view of the projects happening in that language. Certainly it will never be as efficient as a flat list, but it can still be useful for finding interesting things.
- marcinkuzminski 11y agoI never liked the side navigation, we stayed with top one in RhodeCode from beginning and imho it works much better, and i say no for putting icons on everything.
- deleted 11y ago[deleted]
- tonglil 11y agoIf someone wants to keep the tabbed nav sticky to the top of the page, I wrote a Firefox add-on / Chrome extension to do so: https://github.com/tonglil/github-static-nav https://github.com/tonglil/github-static-nav