Commit tips and checklist when making a PR

[pikurasa]

Making a good commit in your pull request helps the community. Among other things, a good commit message helps future contributors debug the code as they can see what the change is within the git history.

Here is a checklist for making a good commit:

• Make sure that your git message is not too long, not longer than the maximum length of fifty characters. If it's too long, the message will be truncated with ellipses.
• Write what the change is in the commit message, not the pull request.
• If you make a mistake, you can fix it. You can rewrite your commit message and force push. To do so, please see our guidance for a checklist.
  • Add the problem to the commit message, as the GitHub issue will be lost and the commit message kept.
  • Add the solution to the commit message, as the GitHub pull request will be lost and the commit message kept.
• Do not make changes unrelated to your stated intent, be more careful, use interactive add of git if necessary to avoid any changes made by your software tools,