|
| 1 | +# Contribution Guidelines |
| 2 | + |
| 3 | +When contributing to `create-t3-app`, whether on GitHub or in other community spaces: |
| 4 | + |
| 5 | +- Be respectful, civil, and open-minded. |
| 6 | +- Before opening a new pull request, try searching through the [issue tracker](https://github.com/t3-oss/create-t3-app/issues) for known issues or fixes. |
| 7 | +- If you want to make code changes based on your personal opinion(s), make sure you open an issue first describing the changes you want to make, and open a pull request only when your suggestions get approved by maintainers. |
| 8 | + |
| 9 | +## How to Contribute |
| 10 | + |
| 11 | +### Prerequisites |
| 12 | + |
| 13 | +In order to not waste your time implementing a change that has already been declined, or is generally not needed, start by [opening an issue](https://github.com/t3-oss/create-t3-app/issues/new/choose) describing the problem you would like to solve. |
| 14 | + |
| 15 | +### Contributing via Codesandbox |
| 16 | + |
| 17 | +You can contribute to this documentation on codesandbox which will automatically run all the setup command for you. [](https://codesandbox.io/p/github/t3-oss/create-t3-app). |
| 18 | + |
| 19 | +### Setup your environment locally |
| 20 | + |
| 21 | +_Some commands will assume you have the Github CLI installed, if you haven't, consider [installing it](https://github.com/cli/cli#installation), but you can always use the Web UI if you prefer that instead._ |
| 22 | + |
| 23 | +In order to contribute to this project, you will need to fork the repository: |
| 24 | + |
| 25 | +```bash |
| 26 | +gh repo fork t3-oss/create-t3-app |
| 27 | +``` |
| 28 | + |
| 29 | +then, clone it to your local machine: |
| 30 | + |
| 31 | +```bash |
| 32 | +gh repo clone <your-github-name>/create-t3-app |
| 33 | +``` |
| 34 | + |
| 35 | +This project uses [pnpm](https://pnpm.io) as its package manager. Install it if you haven't already: |
| 36 | + |
| 37 | +```bash |
| 38 | +npm install -g pnpm |
| 39 | +``` |
| 40 | + |
| 41 | +Then, install the project's dependencies: |
| 42 | + |
| 43 | +```bash |
| 44 | +pnpm install |
| 45 | +``` |
| 46 | + |
| 47 | +### Implement your changes |
| 48 | + |
| 49 | +This project is a [Turborepo](https://turborepo.org/) monorepo. The code for the CLI is in the `cli` directory, and the docs is in the `www` directory. Now you're all setup and can start implementing your changes. |
| 50 | + |
| 51 | +Here are some useful scripts for when you are developing: |
| 52 | + |
| 53 | +| Command | Description | |
| 54 | +| ---------------- | ------------------------------------------------------- | |
| 55 | +| `pnpm dev:cli` | Builds and starts the CLI in watch-mode | |
| 56 | +| `pnpm dev:www` | Starts the development server for the docs with HMR | |
| 57 | +| `pnpm build:cli` | Builds the CLI | |
| 58 | +| `pnpm build:www` | Builds the docs | |
| 59 | +| `pnpm build` | Builds CLI and docs | |
| 60 | +| `pnpm format` | Formats the code | |
| 61 | +| `pnpm lint` | Lints the code | |
| 62 | +| `pnpm lint:fix` | Lints the code and fixes any errors | |
| 63 | +| `pnpm check` | Checks your code for typeerrors, formatting and linting | |
| 64 | + |
| 65 | +When making commits, make sure to follow the [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) guidelines, i.e. prepending the message with `feat:`, `fix:`, `chore:`, `docs:`, etc... You can use `git status` to double check which files have not yet been staged for commit: |
| 66 | + |
| 67 | +```bash |
| 68 | +git add <file> && git commit -m "feat/fix/chore/docs: commit message" |
| 69 | +``` |
| 70 | + |
| 71 | +### When you're done |
| 72 | + |
| 73 | +Check that your code follows the project's style guidelines by running: |
| 74 | + |
| 75 | +```bash |
| 76 | +pnpm check |
| 77 | +``` |
| 78 | + |
| 79 | +Please also make a manual, functional test of your changes. |
| 80 | + |
| 81 | +If your change should appear in the changelog, i.e. it changes some behavior of either the CLI or the outputted application, it must be captured by `changeset` which is done by running |
| 82 | + |
| 83 | +```bash |
| 84 | +pnpm changeset |
| 85 | +``` |
| 86 | + |
| 87 | +and filling out the form with the appropriate information. Then, add the generated changeset to git: |
| 88 | + |
| 89 | +```bash |
| 90 | +git add .changeset/*.md && git commit -m "chore: add changeset" |
| 91 | +``` |
| 92 | + |
| 93 | +When all that's done, it's time to file a pull request to upstream: |
| 94 | + |
| 95 | +```bash |
| 96 | +gh pr create --web |
| 97 | +``` |
| 98 | + |
| 99 | +and fill out the title and body appropriately. Again, make sure to follow the [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) guidelines for your title. |
| 100 | + |
| 101 | +## Translations |
| 102 | + |
| 103 | +For more information on how to help with translation, please see the [contributing guidelines for our docs](https://github.com/t3-oss/create-t3-app/blob/main/www/TRANSLATIONS.md). |
| 104 | + |
| 105 | +## Credits |
| 106 | + |
| 107 | +This documented was inspired by the contributing guidelines for [cloudflare/wrangler2](https://github.com/cloudflare/wrangler2/blob/main/CONTRIBUTING.md). |
0 commit comments