New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TextMatch doesn't work when use Search.Repositories #2385
Comments
Hmmm... that does indeed look unusual. Although the official documentation shows an example using the curl -H 'Accept: application/vnd.github.v3.text-match+json' \
'https://api.github.com/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc' which makes me think that this custom header should be added no matter what the value of Do you want to make a PR to change this behavior and test it out, @DarkMatterV ? |
Okay,I want to do it |
…repositories or issues (google#2385)
…repositories or issues (google#2385)
when i use
Search.Repositories
, setTextMatch = true
, but it doesn't workthis is my code:
I found it in
go-github
, insearch
function, useswitch
to addAccept
to thereq.Header
, it lead to i can't gettext_matches
in reponse when i usecommits
topics
repositories
issues
I don't know why it's designed in this way, and i didn't found other accept values other than
application/vnd.github.v3.text-match+json
on the github restful api, such asapplication/vnd.github.mercy-preview+json
. In fact, i don't know whatapplication/vnd.github.mercy-preview+json
will do even if i read the documentationThe text was updated successfully, but these errors were encountered: