local-ci

You can run GitHub Actions CI jobs locally by executing local CI parity commands that mirror automated checks, ensuring your changes align with repository validation before pushing. Use targeted commands like `pnpm run ci:local --only=build-and-test` to validate specific jobs.

CI parity validation executes the same job shapes used in GitHub Actions locally. You need it after modifying a package to verify that your changes pass all build, test, E2E, and bundle-size checks before pushing to the remote repository.

Yes, running local CI parity commands requires pnpm, Node 20, and Turbo for execution. These tools provide the necessary environment and task orchestration to validate changes against GitHub Actions job shapes locally.

Yes, you can run specific CI jobs locally using targeted execution. The local CI supports package, workflow, E2E, Metro, devtools, bundle-size, and build-and-test scenarios, allowing you to validate only the relevant checks for your changes.

The best way to validate changes locally is using the local CI parity command, such as `pnpm run ci:local --only=build-and-test`. This mirrors the GitHub Actions environment, executing the same job shapes to catch failures before pushing.

Local CI validation may fail due to environment differences, missing pnpm or Node 20 dependencies, or uncommitted changes. Ensure your local environment matches the required Turbo and pnpm setup to accurately mirror the GitHub Actions job shapes.