Overview
Add a safe GitHub Actions CI workflow so every pull request can be checked before maintainers review or merge it.
Problem
As ChainMove opens up to GrantFox contributors, maintainers need automated checks for linting, type safety, and builds. The workflow should use repository secrets safely and must not expose private credentials in logs.
Expected solution
Create .github/workflows/ci.yml that:
- runs on pull requests and pushes to
main
- installs dependencies with
npm ci where possible
- runs
npm run lint
- runs TypeScript checking if a script exists or adds a safe
typecheck script
- runs
npm run build
- injects required environment variables from GitHub Secrets
- avoids deployment or secret-heavy operations on untrusted PRs
Security notes
- Do not echo secrets.
- Do not print environment values.
- Do not add production deployment to this workflow.
- Keep production deploys as a separate maintainer-only workflow.
Files likely involved
.github/workflows/ci.yml
package.json
README.md
Acceptance criteria
- CI runs on PRs and push to
main.
- Lint and build jobs pass.
- The workflow uses safe secret references only.
- No secret value is exposed in logs.
- Fork PRs do not run dangerous deployment steps.
Suggested labels
ci, github-actions, developer-experience, security
Difficulty
Beginner / Intermediate
Overview
Add a safe GitHub Actions CI workflow so every pull request can be checked before maintainers review or merge it.
Problem
As ChainMove opens up to GrantFox contributors, maintainers need automated checks for linting, type safety, and builds. The workflow should use repository secrets safely and must not expose private credentials in logs.
Expected solution
Create
.github/workflows/ci.ymlthat:mainnpm ciwhere possiblenpm run linttypecheckscriptnpm run buildSecurity notes
Files likely involved
.github/workflows/ci.ymlpackage.jsonREADME.mdAcceptance criteria
main.Suggested labels
ci,github-actions,developer-experience,securityDifficulty
Beginner / Intermediate