{"id":68712,"date":"2022-11-15T11:51:04","date_gmt":"2022-11-15T19:51:04","guid":{"rendered":"https:\/\/github.blog\/?p=68712"},"modified":"2022-11-15T10:51:15","modified_gmt":"2022-11-15T18:51:15","slug":"a-better-way-to-search-navigate-and-understand-code-on-github","status":"publish","type":"post","link":"https:\/\/github.blog\/developer-skills\/github\/a-better-way-to-search-navigate-and-understand-code-on-github\/","title":{"rendered":"A better way to search, navigate, and understand code on GitHub"},"content":{"rendered":"

Our mission at GitHub is to build tools to make developers happier and more productive. Great tools eliminate burdens and allow developers to focus on what they do best: building things.<\/em><\/p>\n

But while building, developers don\u2019t just write code\u2014they browse, navigate, sift, and sort through it. Reading code is a hugely important task for developers, whether they are planning and implementing features, investigating bugs or reviewing code. That\u2019s why we built GitHub\u2019s new code search\u2014to help developers search, navigate, and understand code written by them, their team, and the world. Our new code search index includes over 10 billion unique documents across 30+ million repositories (and growing).<\/p>\n

From a technology preview to GitHub.com<\/span><\/a><\/h2>\n

Since we launched the code search technology preview<\/a>, over 100,000 developers joined the waitlist and gained access, giving us tons of valuable feedback.<\/p>\n

Developers loved the ability to instantly find relevant code, use our powerful code navigation, and dig through large and complex codebases. And for many developers, GitHub code search became an essential part of their workflow\u2014something they depend on every day to find the answers they need to do their job.<\/p>\n

We heard your feedback about wanting this for GitHub.com, so at GitHub Universe<\/a> we unveiled the new code search and navigation capabilities we’ve been working on for you.<\/p>\n

Find exactly what you\u2019re looking for \ud83d\udc40<\/span><\/a><\/h2>\n

This beta introduces an all-new search interface in GitHub.com, with suggestions, completions, and the ability to filter results by a wide variety of dimensions (for example, repository, language, symbol, and owner). Backed by our new code search engine, you can search for code using powerful qualifiers, boolean expressions, and even regular expressions.<\/strong><\/p>\n

We\u2019ve developed our new code search engine completely from scratch, with a focus on performance. Most search queries find results in just a few hundred milliseconds\u2014so you can quickly search, iterate, and refine your query to find exactly what you\u2019re looking for.<\/p>\n

\"screenshot<\/p>\n

Our new code search engine actually understands<\/em> code\u2014and brings you the most relevant results first, so you can find answers buried in your codebase.<\/p>\n

Browse, navigate, and dig deeper<\/span><\/a><\/h2>\n

Clicking on a search result is just the beginning of the journey. Developers need to search, browse, and navigate code, find definitions and references, and trace the path of the code through their codebases. That\u2019s why, as part of this beta, we\u2019ve completely redesigned the code view, tightly integrating browsing, search, and code navigation.<\/p>\n

\"Screenshot<\/p>\n

We\u2019ve also added a file tree to the left side of the code view, which puts code in context, showing where it fits into the rest of the repository, and enables developers to easily browse files across their repository.<\/p>\n

\"Side-by-screenshots<\/p>\n

See code search in action<\/span><\/a><\/h2>\n