On this page
Bellows
Secrets
Bellows does not pass all local environment variables into workflows by default.
This is intentional. GitHub Actions workflows can run arbitrary commands, so local secrets should be explicit.
No Secrets
Default behavior:
yaml
secrets:
mode: noneAllow Environment Secrets
To pass selected environment variables to act, use mode: env and list the
allowed names:
yaml
secrets:
mode: env
allow:
- GITHUB_TOKEN
- NPM_TOKENThen run Bellows with those variables set:
Terminal
NPM_TOKEN=... bellows runBellows passes only the names listed under allow.
Audit workflow secret references:
Terminal
bellows secrets auditExample output:
text
[allowed] .github/workflows/ci.yml job publish step Publish uses NPM_TOKEN
[blocked] .github/workflows/ci.yml job publish step Publish uses OTHER_TOKENRecommended Practice
Use low-privilege local tokens.
Avoid deployment credentials in local runs.
Skip deploy jobs unless you have an explicit local deployment simulation.
Do not commit
.envfiles or credential files.