tokens:setup
Show step-by-step instructions for obtaining and configuring the tokens required by SPLENT commands.
Usage
splent tokens:setup
No arguments or options.
Description
Prints instructions for obtaining and setting up the two credentials that SPLENT needs:
| Token | Used by |
|---|---|
GITHUB_USER + GITHUB_TOKEN |
feature:release, feature:clone, feature:versions, feature:upgrade, feature:search, feature:install, check:github |
TWINE_USERNAME + TWINE_PASSWORD |
feature:release, check:pypi |
All tokens go in the workspace .env (loaded by the CLI container at startup).
GITHUB_TOKEN
A GitHub Personal Access Token (classic) with repo scope.
How to get it:
- Go to github.com → Settings → Developer settings → Personal access tokens → Tokens (classic)
- Click Generate new token (classic)
- Enable scope:
repo(full control of private repos) - Copy the token — it is shown only once
Add to your .env:
GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxx
TWINE_USERNAME + TWINE_PASSWORD
A PyPI API token used to publish packages.
How to get it:
- Go to pypi.org → Account settings → API tokens
- Click Add API token
- Choose scope:
Entire accountor limit to a specific project - Copy the token — it is shown only once
Add to your .env:
TWINE_USERNAME=__token__
TWINE_PASSWORD=pypi-xxxxxxxxxxxxxxxxxxxxxxxxxxxx
TWINE_USERNAME is always the literal string __token__, not your PyPI username.
Verify
Once the tokens are set, confirm they work:
splent check:github
splent check:pypi
See also
check:github— verify GitHub token and connectivitycheck:pypi— verify PyPI credentialsfeature:release— requires both tokens