# Contributing to Trigger.dev Thank you for taking the time to contribute to Trigger.dev. Your involvement is not just welcomed, but we encourage it! 🚀 Please take some time to read this guide to understand contributing best practices for Trigger.dev. Thank you for helping us make Trigger.dev even better! 🤩 ## Developing The development branch is `main`. This is the branch that all pull requests should be made against. The changes on the `main` branch are tagged into a release monthly. ### Prerequisites - [Node.js](https://nodejs.org/en) version >=16.x - [pnpm package manager](https://pnpm.io/installation) version 7 - [Docker](https://www.docker.com/get-started/) ### Setup 1. Clone the repo into a public GitHub repository or [fork the repo](https://github.com/triggerdotdev/trigger.dev/fork). If you plan to distribute the code, keep the source code public to comply with the [Apache Licence 2.0](https://github.com/triggerdotdev/trigger.dev/blob/main/LICENSE). ``` git clone https://github.com/triggerdotdev/trigger.dev.git ``` > If you are on windows, run the following command on gitbash with admin privileges: > `git clone -c core.symlinks=true https://triggerdotdev/trigger.dev.git` 2. Navigate to the project folder ``` cd trigger.dev ``` 3. Install the required packages using pnpm. ``` pnpm i ``` 4. Create your `.env` files ``` cp .env.example .env && cp packages/database/.env.example packages/database/.env ``` 5. Open the root `.env` file and fill in the required values Magic Link: Both of these secrets should be random strings, which you can easily generate (and copy into your pasteboard) with the following command: ```sh openssl rand -hex 16 | pbcopy ```
Then set them here:
``` SESSION_SECRET=