Sourcegraph 3.29 is now available! For this release, we introduced search results ranking, made it easier to create Code Insights, and added support for bulk actions with Batch Changes.
We're making search results more relevant, starting with better prioritization of repos vs. code in your search results. Search results and suggestions are now ranked by descending star count on sourcegraph.com and customer instances (for repos with stars), making it easier to find specific repos. Start searching on sourcegraph.com to experience the new ranking.
We are proud to bring you an entirely new visual design for the Sourcegraph UI. The new visual design was developed to help users find references, troubleshoot errors, gain insight, make changes on a massive scale, and read code. Check out our recent blog post to learn more about the new Sourcegraph UI.
You can now create code insights with one click, right from the search query view. Take your search query and turn it into a visualization of your results count in your code over time, to see if your usage of an API, function, or other target is growing or shrinking.
We now autosuggest and autocomplete the repository field in the correct format. The forms also now autosave your configuration, in case you navigate away before you hit "create." (You can clear your existing autosave if you want to start fresh, with the "clear all fields" button.)
Last release we introduced bulk actions, allowing users to comment on hundreds of changesets in a few clicks. We've added two more bulk actions in this release: retry errored changesets and merge.
Merge is released as an experimental feature. It supports merge commit and squash merge on GitHub and GitLab, and merge commit on Bitbucket. For example, you can now filter all changesets that have passed checks and review, and merge them all in a few clicks. Read more about bulk operations.
Code Insights queries can now run concurrently up to a limit set by the
insights.query.worker.concurrency site config.
Code Insights workers now support a rate limit for query execution and historical data frame analysis using the
insights.historical.worker.rateLimit site configurations.
SettingsSubject type now has an
allowSiteSettingsEdits field to allow clients to determine whether the instance uses the
GLOBAL_SETTINGS_FILE environment variable.
Code Insights creation UI now has autosave logic and clear all fields functionality.Repositories
Code Insights creation UI now has suggestions support for the repository fields.Batch Changes
A new bulk operation to retry many changesets at once has been added to Batch Changes.API
Added featured Sourcegraph extensions query to the GraphQL API, as well as a section in the extension registry to display featured extensions.Search
The search page now has a
create insight button to create search-based insights based on your search query.
Added support for Terraform syntax highlighting.Batch Changes
A new bulk operation to merge many changesets at once has been added to Batch Changes.Code Insights
Search-based insight creation UI now supports
count: filter in data series query input.
SSH public keys generated to access code hosts with batch changes now include a comment indicating they originated from Sourcegraph.Search
The copy query button is now permanently enabled and
experimentalFeatures.copyQueryButton setting has been deprecated.
Search streaming is now permanently enabled and
experimentalFeatures.searchStreaming setting has been deprecated.
Stricter validation of structural search queries. The
type: parameter is not supported for structural searches and returns an appropriate alert.
Batch changeset specs that are not attached to changesets will no longer prematurely expire before the batch specs that they are associated with.Code Insights
Code insights line chart no longer has a negative quadrant.Repositories
Correctly handle field aliases in the query (like
repo:) when used with
index filter was removed from search type-ahead suggestions.
Code host connection tokens aren't used for creating changesets anymore when the user is site admin and no credential has been specified.