Skip to content

Document environment variables and drop unused GH_TOKEN wiring#25

Open
askov wants to merge 1 commit intosolana-developers:mainfrom
hoodieshq:docs/env-vars-documentation
Open

Document environment variables and drop unused GH_TOKEN wiring#25
askov wants to merge 1 commit intosolana-developers:mainfrom
hoodieshq:docs/env-vars-documentation

Conversation

@askov
Copy link
Copy Markdown
Contributor

@askov askov commented Apr 20, 2026

Summary

  • Add a single env-vars reference table to the README (required-when, sensitivity, purpose) so prod vs. local setup is no longer implicit.
  • Add .env.example as a committed template — placeholder values only, real .env stays gitignored.
  • ⚠️ Remove the unused GH_TOKEN (singular) from app.yaml and .github/workflows/deploy.yaml. Only GH_TOKENS (plural, comma-separated) is read by src/clients/githubClient.js.

Why

Env-var docs in the README drifted from the code: the old instructions required PROJECT_ID locally (actually bypassed when POSTGRES_STRING is set), referenced a singular GH_TOKEN the code never reads, and gave no guidance on which values are secrets. This PR realigns docs with runtime behaviour and makes the sensitivity of each variable explicit.

Test plan

  • Confirm GH_TOKEN (singular) is not referenced anywhere in src/grep -rn "GH_TOKEN\b" src/ should return nothing.
  • Confirm the existing GH_TOKENS secret is still wired through app.yaml and the deploy workflow.
  • Next deploy to App Engine succeeds and the app starts (GitHub validation still works with GH_TOKENS).
  • New contributor can follow README + .env.example to run the app locally against Cloud SQL Auth Proxy.

Adds a single env-vars reference table to the README (required-when,
sensitivity, purpose) plus a .env.example template so local setup no
longer depends on reading scattered code. Drops the unreferenced
GH_TOKEN from app.yaml and the deploy workflow — only GH_TOKENS (plural)
is consumed by githubClient.js.
Copy link
Copy Markdown

@rogaldh rogaldh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants