fix/users: remove query for usageStatistics#1264
Merged
keegancsmith merged 3 commits intomainfrom Mar 2, 2026
Merged
Conversation
This field was deprecated in March last year and was removed November last year [1]. Before this change any user subcommand just failed. Will be adding some integration smoke tests to catch these sort of issues. Additionally found one place we didn't set Content-Type which Sourcegraph also recently started enforcing. [1]: https://sourcegraph.sourcegraph.com/deepsearch/3e8160f0-e54a-4b0b-b65a-7bd0b78120ae
bahrmichael
approved these changes
Mar 2, 2026
eseliger
approved these changes
Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This field was deprecated in March last year and was removed November
last year 1. Before this change any user subcommand just failed. Will be
adding some integration smoke tests to catch these sort of issues.
Additionally found one place we didn't set Content-Type which
Sourcegraph also recently started enforcing.