-
Notifications
You must be signed in to change notification settings - Fork 165
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
GitHub packages do not fall back to global GitHub token #1866
Labels
bug
Something isn't working
Comments
ImranR98
added
source-specific
This bug/feature affects a specific source
and removed
to check
Issue has not been reviewed
labels
Sep 30, 2024
Not sure what you mean by GitHub "package" - could you provide an example? |
Packages installed from GitHub releases. Added by searching GitHub from Obtainium. For example Obtainium. |
My case:
|
This comment was marked as outdated.
This comment was marked as outdated.
ImranR98
added
TODO
Issue to focus on for the next release
source-specific
This bug/feature affects a specific source
and removed
source-specific
This bug/feature affects a specific source
labels
Oct 1, 2024
ImranR98
pushed a commit
that referenced
this issue
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding a GitHub package without specifying the access token in its options results in quota exceeded errors since the globally configured token is not used. One must repeat the token for every such package, which is tedious.
On top of that, it is impossible to change the per-package token, meaning after one finds that they have too many packages, one has to go through them all and re-add them.
Once the token expires, one would have to re-add all the packages to change the token as well.
The text was updated successfully, but these errors were encountered: