Live data from Hacker News

Redesigning GitHub Repository Page

tonsky.me

1–10 of 315 posts

Re: Redesigning GitHub Repository Page

#4
The only point in the whole article I agree with is that the latest commit per-file isn't particularly helpful. Otherwise I think the changes the author proposes make for a usability downgrade. A cluttered, aimless pile of shipwrecked links and elements floating on the sea of a page.

Re: Redesigning GitHub Repository Page

#5
Two nitpicks:

1. Why are the images cropped so strangely on mobile? It makes this article really hard to read.

2. Shouldn’t the title be “Redesigning the GitHub Repository Page”?

^ And a meta question for programmers, what do you do when English grammar calls for a question mark to be inside your quotation mark at the end of a sentence, but you’re literally quoting something that should not include the question mark? It’s grammatically wrong, but I’ve taken to moving the question mark outside in the case to avoid ambiguity.

Re: Redesigning GitHub Repository Page

#6
Having "branches" and "Pull Requests" tabs on the same level just doesn't make sense :/

The main thing you want to see with the repo page is the code and the readme, i don't want to see all these commit messages or stats. Irrelevant.

This actually made me appreciate Github's current design :)

Re: Redesigning GitHub Repository Page

#7

Two nitpicks: 1. Why are the images cropped so strangely on mobile? It makes this article really hard to read. 2. Shouldn’t the title be “Redesigning the GitHub Repository Page”? ^ And a meta question for programmers, what do you do when English grammar calls for a question mark to be inside your quotation mark at the end of a sentence, but you’re literally quoting something that should not include the question mark?…

I've been ignoring that rule of English grammar for as long as I can remember; it makes no sense.

Re: Redesigning GitHub Repository Page

#8

Two nitpicks: 1. Why are the images cropped so strangely on mobile? It makes this article really hard to read. 2. Shouldn’t the title be “Redesigning the GitHub Repository Page”? ^ And a meta question for programmers, what do you do when English grammar calls for a question mark to be inside your quotation mark at the end of a sentence, but you’re literally quoting something that should not include the question mark?…

I'd title this "Redesigning GitHub Repository Pages". And I don't put punctuation inside quotes, unless I'm quoting an actual person's speech. I guess that's what I find most natural :/

Re: Redesigning GitHub Repository Page

#9
Half of this works well; some of the redesign of tabs, the elimination of icons, and similar changes look great.

On the other hand, showing the last commit and change time for each file is useful. Where is that information now? It's in a linear commit list, which is helpful for different purposes ("when was the repo last updated and what's up?") but doesn't serve the original purposes as well ("when was this file updated?"). At the very least, the last-changed date would help.

Shoving statistics over on the right-hand side makes the page much more crowded; expanding the space available for files and commits would work better. Notice how the commit list has messages truncated; 70-to-80-character commit messages ought to fit comfortably there.

Where does the README appear, here? That tends to be the first thing I'm looking for in a new project, and it doesn't look like this redesign took that into account at all.

The new extra-busy tab bar makes it harder to get at the things you use every day: issues and pull requests.

Post reply on HN