CI: build, typecheck and lint on pull requests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Run next build on pull requests.
This is the highest-value check for this repo: next build type-checks the whole project, so a broken import, a bad prop, or a missing generateStaticParams fails here rather than in review or after merge. Right now nothing verifies that main even compiles.
Scope
A workflow that runs on PRs and pushes to main:
npm cinpm run buildnpm run lint(ESLint config and script already exist, so it is nearly free)
Node 20+.
Note
Build times are small — the current build compiles in a few seconds — so this is cheap to run on every PR.
Part of #38.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the repository's package scripts and existing GitHub Actions configuration. Add a workflow for pull requests and pushes to main that uses Node 20+, runs npm ci, npm run build, and npm run lint. Done means the workflow completes successfully and catches build, typecheck, and lint failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, next.js, node.js, typescript
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100