🤔 Why?

The problem we noticed is that setting up CI is performed once, needs to be researched every time, and is often trial and error driven. The process is repetitive.

We created a tool that bootstraps CI with the most used features, which are ready for customization in the future. Running npx setup-ci generates GitHub workflows for the most popular CI tasks.

📖 Usage

Simply go to your project root directory and run:

npx setup-ci

then select the setup that matches your project - npx setup-ci generates workflows and tries to add missing configs and install necessary dependencies.

If your project has a monorepo structure, run the script from the root directory of the app for which you want to set up workflows.

[!WARNING] If you re-run npx setup-ci in the same project or already have some workflows set up manually, they might get overwritten. Therefore, we recommend running the script with no uncommitted changes, so you can easily inspect the diff after script execution.

💡 Demo

Say we want to set up GitHub actions that run Typescript and Prettier checks on our project every time we create or push to an existing Pull Request. Let's try to use npx setup-ci to do the heavy lifting and generate all the necessary configurations.

Alternatively, we can use flags --preset --ts --prettier to avoid the interactive survey at the beginning of the script. You can check the section below for more information about available flags!

⚙️ Features

• Currently, only GitHub actions are supported as your CI.
• npm and yarn are supported as package managers, and they will be detected automatically.
• Monorepo structure is supported, but make sure you run the script from the app directory, not the monorepo root.

When using npx setup-ci, you can provide additional flags to modify its default behavior.

The following are feature flags that can be used with --preset flag (they are ignored if --preset is not provided).

🔐 Repository secrets

Some workflows generated by npx setup-ci require setting up repository secrets that can be then accessed by workflows as ${{ secrets.* }}. Make sure to read logs printed by the script as you will always be prompted to create secrets if necessary. The following table shows a summary of secrets you might have to create for generated workflows to work properly.

🔍 Troubleshooting

For known issues with npx setup-ci, please check Troubleshooting.

📊 Metrics

By default, npx setup-ci collects anonymous usage data that helps us improve the tool. You can disable it by using the --skip-telemetry option. Collected data consists of timestamp, tool version, selected options, whether the script has been run for the first time and whether it ended with an unexpected error (without stacktrace so that no sensitive PII can be accidentally leaked).

💬 Your feedback

[!IMPORTANT] If you have an issue using npx setup-ci, you can check Troubleshooting and Reported Bugs for a potential solution.

This tool is supposed to be helpful to as many developers as possible - and therefore we are open to your ideas and general feedback! If you want to share your opinion about npx setup-ci or have some thoughts about how it could be further developed, don't hesitate to create an issue or contact the maintainers directly.

🚸 Roadmap

• [x] Build Expo DevClient when fingerprint changes
• [x] Maestro support for E2E tests
• [ ] Different workflows for different branches (ex. PR, main, release)
• [ ] Upload source maps to Sentry
• [ ] Handle different vendors

📋 License

npx setup-ci is licensed under The MIT License.

💸 Credits

This project has been built and is maintained thanks to the support from Software Mansion

setup-ci is created by Software Mansion

Since 2012 Software Mansion is a software agency with experience in building web and mobile apps. We are Core React Native Contributors and experts in dealing with all kinds of React Native issues. We can help you build your next dream product – Hire us.