The Code Tab
¡OH MY SCIENCE EVERYTHING HAS CHANGED! Welcome to the Code tab. GitHub launched over three years ago, but to this day we’ve never touched our main repository navigation structure. This…
¡OH MY SCIENCE EVERYTHING HAS CHANGED!

Welcome to the Code tab. GitHub launched over three years ago, but to this day we’ve never touched our main repository navigation structure. This is the first of many steps designed to take GitHub into the future. We’ve also refreshed a lot of the visuals across the site while we were at it.
The code tab is what your code is and has been. Browse the source, commits, tags, and downloads. The new navigation also tries hard to get out of your way — on subpages we remove extra administrative chrome:

One of my favorite features of the new code tab is how easy it is to switch between branches and tags — just press w (for switch) on any page and you’ll have a nice filterable branch or tag list.

We’ve also changed a great number of small things:
- We’ve added a quick download as zip button to the main repository header (of course you can visit the downloads page to download a tar if you so choose)
- The downloads page now lives under Code
- Repositories now have first-class tags pages at
/[user]/[repo]/tags - The Fork Queue now lives under Network
- The contributors tab now lives under Stats & Graphs
Of course, none of the urls have changed — so your bookmarks should work just fine.
Hope you guys enjoy!
Written by
Related posts
Developer policy update: Transparency, state policy, and what’s ahead
Explore GitHub’s latest transparency data and learn more about policy updates affecting developers and open source.
Developers want more efficient software. Here’s what over 1,000 GitHub users told us they need.
New research from GitHub and Yale Program on Climate Change Communication finds strong demand for tools, measurement, and practical guidance that can help developers reduce wasted compute.
GitHub availability report: August 2026
In August, we experienced five incidents that resulted in degraded performance across GitHub services.