Redesigned navigation available in Public Beta

GitHub's navigation has been redesigned with a new look and improved user experience, and it's available to try in beta.

New breadcrumbs provide a clear understanding of your location within GitHub and its information architecture.

Screenshot of the navigation UI, highlighting the breacrbumbs

Streamlined menus:

There's a new global menu designed to highlight common workflows.

  • You can quickly access links to your dashboard, Issues, Pull Requests, and Discussions, as well as your repos and teams.
  • Your lists of top repos and teams are ordered by your usage, and can be expanded and filtered to quickly find what you're looking for.
  • Access it by clicking the GitHub logo in the upper left corner.

The user menu has likewise been updated with a new design.

  • We've added links to documentation and customer support.
  • You can still access it by clicking your user profile in the upper right corner.

Screenshot of the navigation UI, with the left menu open to reveal the navigational links

The redesigned navigation is optimized to work with the new code search experience and introduces a button to quickly access the command palette.

Faster, more consistent, and more accessible

Under the hood, we have completely rearchitected the navigation across every feature to be faster and more consistent. It's also more accessible, built from the ground up to work with assistive technology.

Join the beta

To access the beta version of our redesigned navigation, go to Feature Preview and enable "Global navigation update."

Expanding the Triage role and introducing new options for how content is reported

We're excited to share four improvements that we think will improve how moderators maintain their communities. Our goal with thesse improvements is to help moderators of large communities distribute the workload of maintaining healthy discourse. The improvements we're proposing are:

  1. Allowing users with the triage role to make the following changes (only within Discussions):
    a. Move Discussions to a different cateogory
    b. Convert Issues to Discussions in bulk
    c. Hide Discussion comments
    d. Edit and delete Discussion comments
  2. Allowing users with the triage role to report content. (Impacts Discussions, Issues, PRs).
  3. Let prior contributors be able to report content by default in new repos. (Impacts Discussions, Issues, PRs).
  4. Maintainers can choose to let ALL users report content. (Impacts Discussions, Issues, PRs).

The first two changes to the triage role impact existing users with that permission. These changes slightly increase the scope of what the role can do – but we believe that these changes are consistent with how the majority of maintainers are trying to use the triage role.

Changes 3 and 4 impact who can report content by default. Moving forward, new repos will get a better default (letting prior contributors report content), but ultimately, we're putting the power in the hands of maintainers to decide how best to run their communities.

For questions or feedback, please visit our community.

See more

Export your sponsorable dependencies and sponsor many in one checkout

gif of completed checkout confetti

Choosing who to sponsor and sponsoring many of your dependencies is now a lot easier! Starting today you can export your list of sponsorable dependencies from the Sponsors Explore page, this gives you a great starting point when making your GitHub Sponsors selections. Once you've made those selections you can upload them in a CSV, review and edit the one-time sponsorships, and checkout in one transaction.

Read the documentation for details or go to Sponsors Explore and get started. Let us know what you think.

See more
View all changes