As we are receiving more contributions 馃殌 馃幐 we'd need to define how to contribute in a more standard manner. Things that **I** like when doing a review of a PR: - [x] has a self-explanatory title - [x] has a great description where the what and why is properly explained - [x] has tests - [x] is never push-forced - [x] updates the docs - [x] passes the CI checks - [x] passes the lint checks - [x] when needed, contains links to existing issues/PRs What things do you see important to address for this project? We could create a PR template including those checks
As we are receiving more contributions 馃殌 馃幐 we'd need to define how to contribute in a more standard manner.
Things that I like when doing a review of a PR:
What things do you see important to address for this project? We could create a PR template including those checks