We want to keep our repository as clean as possible because of that we have strict set of rules how to commit your code to the repository.
If you would not follow them your pull request will be rejected.
In general it's very good practice to do that - always. Version control systems are made so you can track all changes done to the code or data hosted on it. Why would you choose to use it and make big batch commits? If you want to do that you could use dropbox to host your project files instead.
Bad:
Minor changes in player manager.
Good:
Improved get player by id performance.
Brief summary of the commit (72 characters or less).
Optional more detailed description. Notice the space between this and the brief summary message.
This one can be as long as you want - there is no strict limits set by us.
We use rebase strategy for git history, if your git history is not flat and contains various merge commits it will be rejected. Please rebase before sending pull requests.
You can take a look at commit messages from different developers here.
Feel free to join official projects discord and chat with us.