GitHub CLI is soon moving away from storing the token in plain text configuration file. It will prefer to read the token from system's keyring storage.
As an unfortunate result, extensions will start failing now that token isn't in the YAML file anymore. But, we also don't want individual extensions to interface with the keyring. Instead, extensions will now shell out to gh config get oauth_token --host HOSTNAME to obtain the token.
This introduces a dependency on gh proper to be in PATH, but I consider that to be a reasonable request for extensions.
Delegating to the gh executable to obtain the token allows us to fine-tune how GitHub CLI interfaces with keyring storage in the future without affecting extensions again.
GitHub CLI is soon moving away from storing the token in plain text configuration file. It will prefer to read the token from system's keyring storage.
As an unfortunate result, extensions will start failing now that token isn't in the YAML file anymore. But, we also don't want individual extensions to interface with the keyring. Instead, extensions will now shell out to
gh config get oauth_token --host HOSTNAMEto obtain the token.This introduces a dependency on gh proper to be in PATH, but I consider that to be a reasonable request for extensions.
Delegating to the
ghexecutable to obtain the token allows us to fine-tune how GitHub CLI interfaces with keyring storage in the future without affecting extensions again.