1. Ask for why in description to help with troubleshooting in the future 2. Change related PRs to a list so it renders nicer 3. Remove changes.md task in favor of just using milestones to track changes 4. Add reminder to check if API specs need to be updated
27 lines
943 B
Markdown
27 lines
943 B
Markdown
<!--
|
|
Thank you for sending the PR! We appreciate you spending the time to work on these changes.
|
|
|
|
Help us understand your motivation by explaining why you decided to make this change.
|
|
|
|
You can learn more about contributing to appwrite here: https://github.com/appwrite/appwrite/blob/master/CONTRIBUTING.md
|
|
|
|
Happy contributing!
|
|
|
|
-->
|
|
|
|
## What does this PR do?
|
|
|
|
(Provide a description of what this PR does and why it's needed.)
|
|
|
|
## Test Plan
|
|
|
|
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Screenshots may also be helpful.)
|
|
|
|
## Related PRs and Issues
|
|
|
|
- (Related PR or issue)
|
|
|
|
## Checklist
|
|
|
|
- [ ] Have you read the [Contributing Guidelines on issues](https://github.com/appwrite/appwrite/blob/master/CONTRIBUTING.md)?
|
|
- [ ] If the PR includes a change to an API's metadata (desc, label, params, etc.), does it also include updated API specs and example docs?
|