Contributing

Information About Contributing to Project

If you find something missing or something is wrong in this manual, you are welcome to write an issue describing the problem.
If you can, please try to fix the problem yourself.
For minor changes, it is not necessary to create an issue first.

In order to make changes

Fork the repository
Install neded dependencies. This step is important to install husky scripts responsible for verifying your code before push
```
yarn install
```
In your forked repository, make your changes in a new git branch:
```
git checkout -b my-fix-branch master
```
Make your changes and add documentation if needed
Commit your changes using a descriptive commit message that follows conventional commits conventions. Adherence to these conventions is necessary because release notes are automatically generated from these messages.
- Please include issue number.
- If your changes includes breaking changes, please describe it.
- Example:
```
git commit -m "fix: eslint issues (#169)"
```
Push your branch to GitHub:
```
git push origin my-fix-branch
```
In GitHub, send a pull request to nuxt-typo3:develop
Thank you 👏