Skip to content
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

Set GITHUB_TOKEN for cargo-binstall by default #556

Closed
wants to merge 1 commit into from

Conversation

taiki-e
Copy link
Owner

@taiki-e taiki-e commented Jun 22, 2024

#554 (comment)

The fact that cargo-binstall's performance or robustness would be worse without this env var at a high probability is very unfortunate.

cc @NobodyXu

Copy link
Collaborator

@NobodyXu NobodyXu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

I've been reluctant to do this because of the implicit github-token passing.

I think we should put up documentation on this and someway to disable it?

@taiki-e
Copy link
Owner Author

taiki-e commented Jun 22, 2024

the implicit github-token passing

Well, that's what the actions/checkout does, but it might indeed not be a good idea here.

@taiki-e taiki-e closed this Jun 22, 2024
@taiki-e taiki-e deleted the dev-binstall-token branch June 22, 2024 03:51
@NobodyXu
Copy link
Collaborator

I will try to improve on cargo-binstall behavior, ideally users should not have to pass the github token, unless they are really installing a lot of crates or the crate itself doesn't provide any information in manifest and binstall has to figure out itself.

I think we can at least speed it up and avoid the need of token, for crate providing package.binstall with pkg-url

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants