So you want to help? First of all, thank you! There are few rules that we have so anyone can participate while maintaining a good workflow, teamwork, and clean code. These are likely to get modified or added stuff to it, check them regularly.
- Try one commit per implementation.
- Avoid spelling mistakes.
- A code that does not compile or crashes is a code that does not get merged.
- Please, respect the current code architecture; if you think something should change feel free to let know.
- Personal initiative is good, but for the sake of working together in good condition, let other people know what you do or want to do before doing it.
- We will prefer using underscores for function and variable names such as my_function.
- A code with unclear function and variable names will be refused.
- Every command must have a description.
- If there are arguments, the command should have a usage field.
- You need to document every function that is not a command using ''' blocks.
- Try to explain your code using comments as much as possible.
- A code that is not documented is a code that gets refused on review.
- Configs go in the "config.json" file. (see config file for path).
- Any text destined to users has to go in the "strings.json" file. (see config file for path).
If you have contributed to the bot, let people know by adding your name and the features you have implemented at the bottom of the list on the README.md. You can also add more features beneath your name if you contribute again in the future.