2 ms·
The first two have have finally been fixed more or less but: The compact navigation bar hides the branch (this part has been fixed). Scroll down and you can n
by inferiorhuman 3y ago
The first two have have finally been fixed more or less but:
The compact navigation bar hides the branch (this part has been fixed). Scroll down and you can no longer jump to a different branch without scrolling back to the top of the page… which takes a while because the code view widget (UGH) punts navigation key presses off into a black hole.
The new symbol navigator only links to the default branch even if you're on a different branch.
The compare branches button is gone. You have to open a pull request to compare branches (or manually craft the path).
Hyperlinks within markdown that reference the repo only go to the default branch.
Searching within a repo only searches default branch even if you're searching from a different branch. Granted the search results have never been good, but still.
More or less pick a non-default branch and experiment a little. Chances are you'll be forced back to the default branch in short order. Even when the ref name is a parameter in the URL. And that's about the nicest thing I can say about the new Github UI. Pretty much everything else is just worse universally (blurry text, laggy find within page, nothing rendered if javascript is disabled, etc, etc, etc).
- justinclift 3y agoOuch. Yeah, those sound like a pain. I don't like the recent UI overhaul much either, as it makes navigating around a bunch harder in most situations. :/
- inferiorhuman 3y agoYeah, it's especially unfortunate with all the vendor lock-in that Github's managed. Jumping ship to something with a usable interface means not contributing to a huge number of open source projects.