Good code is tested, designed for change, easy to understand and able to cope when things go wrong.
Good pull requests are descriptive, small and short-lived.
- Description explains what you have done and why.
- Tests have been written (or you have explained why you don't need tests).
- Documentation/comments have been added/updated.
- The code is well-designed and able to cope with change.
- The code is easy to understand.
- Tests cover happy and unhappy paths in the code.
- Tests are green on CI (or pulled/tested on your machine).