A smarter, more complete-y search bar
We often like to think of text as a UI at GitHub. We use text to navigate our text editors, we use keyboard shortcuts to delete our email, and we…
We often like to think of text as a UI at GitHub. We use text to navigate our text editors, we use keyboard shortcuts to delete our email, and we use application launchers to navigate our computers.
The command bar was one of our latest attempts at text as UI on GitHub, but it didn’t quite feel right. So today we’re launching a new redesigned search bar. Go ahead and give it a try.
Suggestions for you
If you’re logged in, the search bar will give you suggestions for things you care about.
- Users you follow
- Repositories you’ve starred or contributed to
- Issues you’re watching across the site
Repository aware
If you’re already browsing a repository, we’ll tweak the suggestions to be repository aware. That means we’ll autocomplete issues, pull requests, and files for just that repository.
Fewer commands, more completes
In order to do this we’ve had to strip out some of the less used commands previously supported in the command bar. You will no longer be able to follow/unfollow watch/unwatch from the command bar. We also removed some of the link jumping commands found in the my
context and repository issues context.
Jump to anything with s
and /
If you want to jump to the search bar immediately, use the hotkeys s
or /
and we’ll autofocus the search field. We think it’s an awesome way to jump to anywhere you want in GitHub.
Hope you enjoy!
Written by
Related posts

From MCP to multi-agents: The top 10 new open source AI projects on GitHub right now and why they matter
Get insights on the latest trends from GitHub experts while catching up on these exciting new projects.

Racing into 2025 with new GitHub Innovation Graph data
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through December 2024.

GitHub Availability Report: March 2025
In March, we experienced one incident that resulted in degraded performance across GitHub services.