We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
If you have suggestions for how this project could be improved, or want to report a bug, open an issue! We'd love all and any contributions. If you have questions, too, we'd love to hear them.
We'd also love PRs. If you're thinking of a large PR, we advise opening up an issue first to talk about it.
- Fork and clone the repository.
- Configure and install the dependencies:
bun install
. - Make sure the tests pass on your machine:
bun test
. These tests also apply the linter, so there's no need to lint separately. - Create a new branch:
git checkout -b my-branch-name
. - Make your change, add tests, and make sure the tests still pass. You can find the tests in the
src/tests
directory. - Push to your fork and submit a pull request.
- Wait for your pull request to be reviewed and merged.
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
- Write and update tests. You can find examples of how to do this in the
src/tests
directory. - Keep your changes as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
- Write a good commit message that conforms to (conventional commits)[https://www.conventionalcommits.org/]. This makes it easier to understand what your code is doing and why, which makes reviewing and maintaining it easier.
Work in Progress pull requests are also welcome to get feedback early on, or if there is something blocked you.
- Fork and clone the repository.
- Install dependencies:
bun install
. - Build the project:
bun tsc
. - Start the project:
bun start:watch
.
Copy .env.example
to .env
and update the fields with your own information. For more details, refer to the Environment Setup section in the README.