1  # Contributing
 2  
 3  Hello, and thank you for taking the time to read the contributing guidelines for Duper! Please read through our [Code of Conduct](./CODE_OF_CONDUCT.md) as well.
 4  
 5  Here are some ways to contribute to the project:
 6  
 7  ## Creating issues
 8  
 9  Please search the [existing issues](https://github.com/EpicEric/duper/issues) for answers or previous discussions before creating your own issue.
10  
11  When contributing to a specific module in this project, include its name in the title of your issue. For example: "@duper-js/wasm: Add tests"
12  
13  ## Submitting changes
14  
15  In the case that you'd like to make contributions to Duper, create an issue first if one does not exist. Also include the name of the improved module if applicable, for example: "@duper-js/wasm: Add tests"
16  
17  If you wish to contribute changes to Duper, please [fork the repository](https://github.com/EpicEric/duper/fork), push your modifications to a branch, and create a [pull request](https://github.com/EpicEric/duper/compare). Make sure to [link to the original issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) in your PR's body.
18  
19  Please add a short description of any user-facing changes to the top of the CHANGELOG.md of the appropriate module(s), under the "Unreleased" section (or create one if it does not exist). The changelog should adhere to [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and it must emphasize any breaking changes.