We want Sourcegraph to be:
This roadmap is a curated list of what we are working on now and the direction that we want to move in over the next 12 months. See the Sourcegraph master plan for our high-level product vision.
We ship a release on the 20th day of each month.
Next release: Sourcegraph 3.6 (ships on July 20, 2019).
We’re continually improving Sourcegraph’s core features for developers:
We’re also working toward making Sourcegraph the infrastructure for developer tools and data, with integration into the entire developer workflow (in the editor, code review, and anywhere else they interact with code). In addition to helping developers, this also helps engineering leaders and internal tools teams solve organization-wide problems.
|🏃||Features we are actively working on.|
|🙋||We are hiring for all teams, but especially for these roles.|
Owners: @ijt, @attfarhan, @kzh
The goal of search is to help you find code. Here are some search projects we’re planning to work on or already working on to do that more effectively:
:[foo]will match meaningful chunks of code.
We want to help you stay on top of the code changes you care about, and are working to improve saved searches with better notifications, better integration with code reviews and PRs, and an easier way to add new saved searches and triage results.
Owners: @lguychard, @chrismwendt, @felixfbecker, @vanesa
Sourcegraph helps developers navigate code by providing code intelligence when browsing code on Sourcegraph or on supported code hosts (like GitHub) via our browser extension. Code intelligence includes hover tooltips, go-to-definition, find-references, and other capabilities contributed by Sourcegraph extensions like Codecov, Sentry, LightStep, and Datadog.
Owners: @keegancsmith, @tsenart, @mrnugget
We will let you perform safe, large-scale refactors of code across repositories, services, and languages.
Owners: @beyang, @slimsag, @ggilmore
We want to make it easy to set up a self-hosted Sourcegraph instance in minutes, locally or on the most popular cloud providers. It needs to scale to the needs of organizations with thousands of developers, tens of thousands of repositories, and complex cluster and security needs.
Owners: We’re hiring! 🙋
Owners: We’re hiring! 🙋
The Sourcegraph extension API allows developers to enhance their code review workflow with custom data. We’re working to make the extension API and extension registry even more powerful and useful.
Sourcegraph integrates with many editors. We want to make it super fast to get the answer you need on Sourcegraph when you’re in your editor, without switching to your browser and losing focus. We’re focused on solving problems for you that local editor search and navigation can’t answer.
We want Sourcegraph to be the infrastructure for developer tools and data inside your organization, so you can:
By “developer tools and data”, we mean things like:
Your existing tools to handle these things would integrate with Sourcegraph; no need to switch.
We will let you build and roll out developer tools to every developer in your organization, with seamless integration into the editor, code review, and anywhere else developers interact with code.
Example: You want to encourage better testing among developers in your organization, so you’ve started measuring test coverage in CI. With Sourcegraph, you’d also be able to roll out (optional) test coverage visual overlays to all developers in their editor and code review tool. This would make test coverage more useful and accessible to developers while coding and reviewing, which will yield much faster improvements to your testing culture.
Example: You want to automatically ingest crash logs from your application and create issues from them. To do so, you’d build a tool that parses the stack traces and uses the Sourcegraph API to gather the information to include in the issue: assignment to the code owner of the most recently changed method in the stack trace, a link to the associated code review, logs and traces related to the stack trace, and a list of other services that depend on this code (to help triage). Without the infrastructure Sourcegraph will provide, this kind of automation would be extremely hard to build and fragile.
We will let you connect your local editor to your organization’s Sourcegraph instance and immediately get code intelligence, builds, tests, and other development tools on all of your code.
We will let you use data derived from development to make better decisions. You will be able to export this data to your preferred reporting dashboard.
We will let you enforce policies and processes around security, compliance, and licensing in a developer-friendly way.
Example: For companies needing to be PCI compliant, PCI DSS 3.0 rule 6.3.2 requires someone other than the author to review each code change. Using Sourcegraph’s knowledge of the dependency graph for libraries and services, you’ll be able to guarantee that all code used by a PCI-compliant system has been properly reviewed (prior to merging and before release), even if it’s in a separate repository or tree.