-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
BUG: cannot access private repositor with GITHUB_TOKEN provided #1681
Comments
We only use GITHUB_TOKEN to speedup the access, and we actually have a few requests created without the token. |
adding debug info
|
Thanks, just need some help: can you If that works, then I could fix it by simply adding it to all repository access. |
maybe im not doing it right, but
is still giving me a 404 (with the actual token) |
what does seem to work is
then pulling the asset id from that, and then calling
docs: https://docs.github.com/en/rest/releases/assets?apiVersion=2022-11-28#get-a-release-asset |
Thanks I see, it would require some more modifications to cargo-binstall then. |
NOTE to myself, cargo-binstall would also need https://docs.github.com/en/rest/repos/repos?apiVersion=2022-11-28#get-a-repository |
For listing repository: r#"
query {{
repository(owner:"{owner}",name:"{repo}") {{
owner {{
login
}}
name
private: isPrivate
}}
}}"# Example output: {
"data": {
"repository": {
"owner": {
"login": "cargo-bins"
},
"name": "cargo-binstall",
"private": false
}
}
} |
we are currently facing an issue, and not sure if we are doing something wrong
it is a private github repo, and the crate is not in any registry. the release artifact is stored in the github releases.
it seems the github token works for pulling the Cargo.toml from the github repo, but then fails for some other requests for the same url? The github token has all privileges
Is --git the correct mode to use?
Originally posted by @scullionw in #1535 (reply in thread)
The text was updated successfully, but these errors were encountered: