GitHub REST API
sort query parameter removal on GET /search/code
Stopped workingSubscribe to GitHub REST APIShare
Calls to GET /search/code, query parameter sort on GitHub REST API stopped working on April 10, 2023.
Calls it hits
GET /search/codequery parameter sort
What to use instead of these calls
None: code search results are always sorted by best match; sort client-side if needed.
In GitHub REST API's words
We are deprecating support for sorting code search results. Once these changes take effect, all code search results will be sorted by best match.
Facts
- API
- GitHub REST API
api.github.com - Kind
- Parameter removal
- Announced
- March 10, 2023
- Takes effect
- April 10, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against GitHub REST API's own pages
Questions
When does this change take effect?
Calls to GET /search/code, query parameter sort on GitHub REST API stopped working on April 10, 2023.
What happens to calls after April 10, 2023?
They have failed since April 10, 2023.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from GitHub REST API 10
-
/repos/{id}/{id}/import*Endpoint removal Stopped working -
/repos/{id}/{id}/tags/protection*Endpoint removal Stopped working -
/orgs/{id}/projectsEndpoint removal Stopped working -
/orgs/{id}/teams/{id}/projects*Endpoint removal Stopped working -
/projects/*Endpoint removal Stopped working -
/repos/{id}/{id}/projectsEndpoint removal Stopped working -
/teams/{id}/projects*Endpoint removal Stopped working -
GET /users/{id}/projectsEndpoint removal Stopped working -
POST /user/projectsEndpoint removal Stopped working -
GET /enterprises/{id}/settings/billing/actionsEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.