# Contributing in rs-jest Here are some the guidelines for you, our beloved contributor 😘 - [Questions and Problems](#question) - [Issues and Bugs](#issue) - [Feature Requests](#feature) - [Pull Request Submission Guidelines](#submit-pr) - [Commit Message Conventions](#commit) ### Got a Question or Problem❓ You can use the Github Issue for asking a question. ### Found an Issue or Bug❓ Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available. We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we suggest that you to provide a minimal reproduction scenario (github repo or failing test case). Having a live, reproducible scenario gives us a wealth of important information without going back & forth to you with additional questions like: - version of nodejs used - version of git you use - version of the webassembly-loader you are using - the use-case that fails (if possible and not become a burden for you 😉) A minimal reproduce scenario allows us to quickly confirm a bug (or point out config problems) as well as confirm that we are fixing the right problem. We will **not** be insisting on a minimal reproduce scenario. However, we will **ask** you if you can provide us a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs. We understand that sometimes it might be hard to extract essentials bits of code from a larger code-base but we really need to isolate the problem before we can fix it. ### Feature Requests❓ You can _request_ a new feature by creating an issue on Github. If you would like to _implement_ a new feature, we suggest you to submit an issue first to make sure that particular feature is makes sense for the project. ### Pull Request Submission Guidelines Before you submit your Pull Request (PR) consider the following guidelines: - Search Github for an open or closed PR that relates to your submission. You don't want to duplicate effort. - Commit your changes using a descriptive commit message that follows our [conventionalcommits.org conventions](#commit). Adherence to these conventions is necessary because release notes are automatically generated from these messages. - Fill out our `Pull Request Template`. ### Contribution Commit Conventions Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**: ```xml ():