github-actions-ci

To generate GitHub Actions CI workflows for a Next.js project, this tool detects your package.json scripts and existing configurations to safely scaffold a tailored .github/workflows/ci.yml file. It automatically includes lint, typecheck, unit tests, and build matrices without overwriting custom setups.

Yes, you can set up GitHub Actions CI for Expo projects safely. The generator detects existing .github/workflows/ files and avoids overwriting custom CI configurations, providing a non-destructive scaffold that you can review and customize.

The CI workflow handles Playwright browsers and preview deploys by automatically including them in the generated configuration when appropriate for your project. It applies safe defaults and provides guidance for reviewing these optional preview deployments.

Yes, the generated GitHub Actions CI includes optional Supabase schema checks and RLS testing. It supports Expo and Next.js projects by detecting your specific requirements and adding these checks to the workflow when appropriate.

The best way to add lint and typecheck steps to GitHub Actions CI is using a detection-first generator that reads your package.json scripts. It ensures these steps are automatically included with safe defaults tailored to your Next.js or Expo environment.

The generated CI workflow avoids modifying custom configurations to ensure a safe, non-destructive setup process. By detecting existing .github/workflows/ files first, it preserves your custom CI logic while scaffolding complementary lint, test, and build matrices.