First off, thank you for considering contributing to this project.
Please follow these guidelines for helping us to better address your issue, assessing changes, and helping you finalize your pull requests. There are many ways to contribute, from writing examples, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into the module itself.
This project adheres to the Contributor Covenant Code of Conduct, please read it and follow it before contributing. If you find someone that is not respecting it please report its behaviour.
There are several ways you can contribute to [Project Name]:
- Report a bug
- Suggest a new feature
- update documentation
- Fix a bug or implement a feature
- If you're not sure where to start, take a look at our issue tracker to see if there are any open issues that interest you.
To get started contributing, you should first fork the repository and then clone it to your local machine:
git clone https://github.com/adeojoemmanuel/customized-exception-filters-nestjs
Next, create a new branch for your changes:
git checkout -b my-new-feature
Make your changes and commit them with a descriptive commit message:
git commit -m "(task-last-task-number+1) Add some feature"
Push your changes to your forked repository:
git push origin my-new-feature
Finally, submit a pull request to the original repository. We'll review your changes and provide feedback as soon as possible.
Before reporting a bug please search if there isn’t already a similar issue already open. If you find a similar issue that is already closed, open a new one and include a link to it inside the body of the new one.
Before starting to implement a new feature, open the relative issue for starting an open discussion on where is can be relevant and expose alternative solutions or potential pitfall that you can encounter. Fill all the information required by the template.
If you want to fork our project, you could make it and keep in sync with our template. All contribution which could improve the existent code base are welcome!
To keep a fork up to date, you can follow this GitHub guide. For all the information about forks, see this link.