Problem
The repository workflows require Vercel secrets, but current docs do not clearly document them. This makes CI/CD setup error-prone for new maintainers and forks.
Missing documentation
Please document required GitHub Actions secrets for deployment workflows:
VERCEL_TOKEN
VERCEL_ORG_ID
VERCEL_PROJECT_ID
Where this is used
.github/workflows/vercel_deploy.yaml
.github/workflows/deploy_preview.yml
.github/workflows/remove_deploy_preview.yml
Suggested fix
Add a CI/CD prerequisites section in README.md (or a dedicated docs page) that includes:
- Required secrets and what each is used for.
- Which workflows depend on each secret.
- A short setup guide for adding secrets in GitHub repo settings.
- Expected behavior when secrets are missing (workflow failures).
Acceptance criteria
Problem
The repository workflows require Vercel secrets, but current docs do not clearly document them. This makes CI/CD setup error-prone for new maintainers and forks.
Missing documentation
Please document required GitHub Actions secrets for deployment workflows:
VERCEL_TOKENVERCEL_ORG_IDVERCEL_PROJECT_IDWhere this is used
.github/workflows/vercel_deploy.yaml.github/workflows/deploy_preview.yml.github/workflows/remove_deploy_preview.ymlSuggested fix
Add a CI/CD prerequisites section in
README.md(or a dedicated docs page) that includes:Acceptance criteria