chore: replace RELEASE.md with CONTRIBUTING.md

Author: erezrokah

CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# Contributions
+
+🎉 Thanks for considering contributing to this project! 🎉
+
+These guidelines will help you send a pull request.
+
+If you're submitting an issue instead, please skip this document.
+
+If your pull request is related to a typo or the documentation being unclear, please click on the relevant page's `Edit`
+button (pencil icon) and directly suggest a correction instead.
+
+This project was made with ❤️. The simplest way to give back is by starring and sharing it online.
+
+Everyone is welcome regardless of personal background. We enforce a [Code of conduct](CODE_OF_CONDUCT.md) in order to
+promote a positive and inclusive environment.
+
+## Development process
+
+First fork and clone the repository. If you're not sure how to do this, please watch
+[these videos](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
+
+Run:
+
+```bash
+npm install
+```
+
+Make sure everything is correctly setup with:
+
+```bash
+npm test
+```
+
+## How to write commit messages
+
+We use [Conventional Commit messages](https://www.conventionalcommits.org/) to automate version management.
+
+Most common commit message prefixes are:
+
+* `fix:` which represents bug fixes, and generate a patch release.
+* `feat:` which represents a new feature, and generate a minor release.
+* `feat!:`, `fix!:` or `refactor!:` and generate a major release.
+
+## Releasing
+
+1. Merge the release PR
+2. Run `npm publish`