Contributing guidelines

[BoomerScratch]

For #20, we need to create a contributing guidelines. What should we write for the contributing guidelines?

[tb148]

Quoted from #20:

Things I think worth including:

1. Semantic Versioning
2. Conventional Commits

Also I think we can create a draft poll request for that.

[WorldLanguages]

Not sure. Anyone should be able to contribute as long as they know git and JavaScript basics

[BoomerScratch]

Contributing guidelines

For anyone who knows Git and JavaScript basics: feel free to contribute to this repository! Our code is open source. Be sure to follow our code of conduct.

Filing issues

Found a bug? Report it! Be sure to check if it is already reported by using the search bar here. If there are no similar issues, you can create a new one. We will take a look at it.

Also, feel free to ask questions, suggest new features, and more.

Creating pull requests

Contributions are welcome! Be sure to file an issue first (see above). If you know a fix for that issue, or you know a fix for a different one, you can create a pull request. Fork this repository, create a new branch from the 'master' branch, and make your changes on the new branch. Now, create a pull request on the origin repository (ScratchAddons/ScratchAddons). We will review your pull request.

What do you guys think?

[WorldLanguages]

@BoomerScratch LGTM

[tb148]

Things I think worth adding:

1. Semantic Versioning
2. Conventional Commits

[WorldLanguages]

@tb148 they feel like too much for this project imo.