archgate credential

Supplies git with a valid access token for Archgate plugin repositories. You do not normally run this command yourself — git invokes it, and archgate login registers it for you.

archgate credential get

Plugin repositories are cloned over HTTPS from plugins.archgate.dev, and git authenticates those requests itself rather than going through the CLI. Access tokens are short-lived, so a token written once into your credential manager would stop working within the hour. This helper closes that gap: git asks it for credentials on each request, and it answers with a cached access token, renewing it from the stored refresh token only once it has lapsed.

The command speaks git’s credential helper protocol on standard input and output. It answers only for plugins.archgate.dev and stays silent for every other host, so credentials for the rest of your remotes keep using whatever helper you already configured.

Subcommands

Subcommand	Description
archgate credential get	Print credentials for a plugin repository
archgate credential store	Accept a credential from git (no-op)
archgate credential erase	Drop the cached access token when git reports it rejected

store is deliberately a no-op: tokens come from archgate login, so there is nothing for git to teach the CLI.

erase drops only the cached access token and keeps your session. Git erases whenever the credentials it was given are rejected, and a single 401 — an access token that slipped past the renewal window, or a transient error from the plugins host — should not cost you a full sign-in. The next request renews from the refresh token.

Configuration

archgate login writes the following to your global git config:

[credential "https://plugins.archgate.dev"]
  helper =
  helper = !/home/you/.archgate/bin/archgate credential

The empty first entry resets any helper inherited from a broader config scope, so archgate is the only helper consulted for this host. The executable is recorded by absolute path, so git started by an editor or a GUI client finds it without your shell’s PATH. archgate login logout removes both entries.

Examples

Inspect what git receives:

printf 'protocol=https\nhost=plugins.archgate.dev\n\n' | archgate credential get

protocol=https
host=plugins.archgate.dev
username=yourname
password=eyJhbGciOiJFUzM4NCIsInR5cCI6ImF0K2p3dCJ9...

When you are signed out, the command prints nothing and exits successfully, which tells git to fall through to its other helpers:

archgate login logout
printf 'protocol=https\nhost=plugins.archgate.dev\n\n' | archgate credential get

Troubleshooting

git clone prompts for a username and password

The helper is not registered. Run archgate login again, or check the configuration directly:

git config --get-all credential.https://plugins.archgate.dev.helper

The output should list an empty line followed by !, the absolute path of the archgate executable, and credential. If it does not, the CLI could not write your global git config — confirm git config --global --list works.

The helper is registered but credentials are still rejected

Confirm you are signed in with archgate login status. If the refresh token has expired or been revoked, the helper returns no credentials and reports the error rather than staying silent. It reads only the token set stored by archgate login; a token issued before this flow existed is never served to git. Run archgate login again.