Open KiaraGrouwstra opened 5 months ago
Check if your GITHUB_TOKEN is expired in $HOME/.config/hub
or $HOME/.config/gh/config.yml
i used a fresh github token.
my gh auth login
did complain about gh/config.yml
being read-only (being symlinked by nix), tho with such login succeeding to let gh
use the credential led me to believe this might have worked.
that doesn't explain to me tho why passing the token by env var (on both nix-review pr <number>
and nix-review post-result
) or by --token
would fail as well tho.
If you create a new token manually here: https://github.com/settings/tokens with the permissions to create issue commends, does it work than?
giving the token (passing by env var) read/write permissions on issues and PRs doesn't seem to change anything for me. i gotta say i'm not sure on precedence rules tho, so i'm not sure if this is actually the token it's using.
If you pass it via --token
than it overwrites anything else. Environment variables have higher precedence over configuration files.
thanks, retried using --token
just in case, but same result
I've been having this issue too, with a token with these permissions. Tried --token
but also didn't work. Got HTTP error 403: Forbidden.
When I use a classic personal access token with repo permissions, it works. So it looks like fine-grained tokens might not be supported yet, or I am not selecting the right permissions scopes.
the classic token works for me as well. perhaps we could clarify that in the docs?
@Mic92
this is the first time i'm trying
nixpkgs-review
, and its GET-like commandcomments
works fine for me. using commands likepost-result
tho yields me an HTTP Forbidden error:i've tried passing account credentials in different ways; by env var, by
gh
or by--token
.version:
my github token has the rights to access all repos (read/write), with no other special settings.
would there be a good way to debug this?