What
Configure automatic deployment preview environments for every pull request so reviewers can test changes in a live environment before merging.
Why
Code review alone can't catch all issues. Preview environments let reviewers interact with the actual application, test features, and verify changes work correctly before approving PRs.
Scope
In scope:
- Configure Vercel, Netlify, or similar for PR preview deployments
- Each PR gets a unique preview URL
- Preview environment uses development API endpoints
- Preview URL is posted as a PR comment automatically
- Environment variables are managed per-environment
Out of scope:
- Production deployment pipeline
- Custom domain configuration
- Database seeding for previews
- Multi-region deployment
Acceptance Criteria
Technical Context
- Check if the project already has Vercel/Netlify integration
app/next.config.js for environment-specific config
- GitHub Actions or platform-native integration
What
Configure automatic deployment preview environments for every pull request so reviewers can test changes in a live environment before merging.
Why
Code review alone can't catch all issues. Preview environments let reviewers interact with the actual application, test features, and verify changes work correctly before approving PRs.
Scope
In scope:
Out of scope:
Acceptance Criteria
Technical Context
app/next.config.jsfor environment-specific config