# Pull Request Template

\#Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

\## Type of change

Please delete options that are not relevant.

\- \[ ] Bug fix (non-breaking change which fixes an issue)

\- \[ ] New feature (non-breaking change which adds functionality)

\- \[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

\- \[ ] This change requires a documentation update

\# How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.&#x20;

\- \[ ] Test A

\- \[ ] Test B

\# Checklist:

\- \[ ] I have performed a self-review of my own code

\- \[ ] I have commented on my code, particularly in hard-to-understand areas

\- \[ ] I have made corresponding changes to the documentation

\- \[ ] My changes generate no new warnings

\- \[ ] I have added tests that prove my fix is effective or that my feature works

\- \[ ] New and existing unit tests pass locally with my changes

\- \[ ] Any dependent changes have been merged and published in downstream modules

\
This template is adapted from [EmbededArtistry](https://embeddedartistry.com/blog/2017/08/04/a-github-pull-request-template-for-your-projects/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.appflowy.io/docs/appflowy/community/appflowy-mentorship-program/pull-request-template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
