Each Pull Request should ideally focus on one single issue or feature. Avoid including unrelated changes. Break down larger changes into smaller, more manageable, and understandable units.
Clearly explain the purpose and context of the Pull Request. Provide a concise summary of the changes made, why they are necessary, and any relevant information that can help reviewers understand the intention behind the code changes.
Ensure that the code changes have been thoroughly tested and do not introduce new issues. We recommend opening a draft pull request to help you review your PR.
Ensure that "All checks have passed", that you've tested and reviewed your PR, and that the description and checklist are properly filled before assigning reviewers. Ask for reviews on complete PRs, not drafts.
Address any concerns or questions raised by reviewers and make necessary adjustments to your code as suggested. Keep the Pull Request up to date with the latest changes.