Why:
We would like to add a bit more structure to the way we describe pull requests, and also introduce a checklist so that we don't miss any important steps when doing the change (especially, testing)
Sections:
Purpose - brief summary of the idea of the change
Summary - a list of key changes
Testing - some evidences the fix/feature works (Postman/curl screenshot(s) etc)
Checklist - the list of thing we need to do before merging any PR. If something is not applicable to the change, it is just marked as Checked
Why: We would like to add a bit more structure to the way we describe pull requests, and also introduce a checklist so that we don't miss any important steps when doing the change (especially, testing)
Sections: