Using token from GitHub CLI (gh) doesn't seem to work

[pbek]

Thank you for this wonderful way to test PRs!

Although, using the token from GitHub CLI (gh) doesn't seem to work for me.
nixpkgs-review-2.9.1 from the nix store.
gh version 2.29.0 (1980-01-01) from the nix store.

I'm logged in into gh (just got a fresh token again).
But my ~/.config/gh/hosts.yml looks like this, no token there:

github.com:
    user: pbek
    git_protocol: ssh

nixpkgs-review says:

Posting PR comments requires a Github API token; see https://github.com/Mic92/nixpkgs-review#github-api-token

[figsoda]

it might have something to do with cli/cli#7276

[pbek]

Seems like the keyring is now used for storage:

https://github.com/cli/cli/blob/bd65e488a4e91ac5442c71b61a352ce679073e39/internal/config/config.go#L225-L230

[wegank]

Also encountered this on a freshly-installed NixOS instance.

A temporary fix is to gh auth login --insecure-storage.

[pbek]

https://github.com/zalando/go-keyring is used in the GitHub CLI to access the keyring, I wonder if nixpkgs-review can (is allowed to) load the token of the GitHub CLI.

[pbek]

I can see the token in kdewallet:

gh auth token also prints the token, maybe that could be used by nixpkgs-review.

[Mic92]

Is there some cli tools present in those desktop environments to easily access keyrings? Otherwise I would just start adding a nixpkgs-review configuration to store secrets (maybe using python's new toml parser).

[pbek]

I wouldn't bother, if you want to execute a CLI tool you can as well run gh auth token in my opinion.

[Mic92]

Ah. I wasn't aware of this option.

[pbek]

Thank you very much!