feedback + PR template

Author: hallvictoria

.github/PULL_REQUEST_TEMPLATE.md

@@ -12,14 +12,33 @@ This checklist is used to make sure that common issues in a pull request are add
 This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
 -->
 
-### PR information
-<!-- You can mark the following checkboxes as [x] to mark them during the PR creation itself. -->
-- [ ] The title of the PR is clear and informative.
-- [ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, [see this page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md).
-- [ ] If applicable, the PR references the bug/issue that it fixes in the description.
-- [ ] New Unit tests were added for the changes made and CI is passing.
-
-### Quality of Code and Contribution Guidelines
-- [ ] I have read the [contribution guidelines](https://github.com/Azure/azure-functions-python-worker/blob/master/.github/CONTRIBUTING.md).
+## Pull Request Checklist
+<!--
+Please fill out the following checklist to ensure compatibility across Python versions and programming models.
+You can mark the following checkboxes as [x] to mark them during the PR creation itself.
+-->
+### Host-Worker Contract
+- [ ] Does this PR impact the host-worker contract (e.g., gRPC messages, shared interfaces)?
+   - If yes, have the changes been applied to:
+      - [ ] azure_functions_worker (Python <= 3.12)
+      - [ ] proxy_worker (Python >= 3.13)
+   - If no, please explain why:   
+
+### Worker Execution Logic
+- [ ] Does this PR affect worker execution logic (e.g., function invocation, bindings, lifecycle)?
+If yes, please answer the following:
+
+**Python Version Coverage**
+   - [ ] Does this change apply to both Python <=3.12 and 3.13+?
+   - If yes, have the changes been made to:
+      - [ ] azure_functions_worker (Python <= 3.12)
+      - [ ] azure_functions_worker_v1 / azure_functions_worker_v2 (Python >= 3.13)
+   - If no, please explain why:
+
+**Programming Model Compatibility (for Python 3.13+)**
+- Does this change apply to both:
+   - [ ] V1 programming model (azure_functions_worker_v1)?
+   - [ ] V2 programming model (azure_functions_worker_v2)?
+- Explanation (if limited to one model):
 
 <!-- Thanks for using the checklist -->

.gitignore

@@ -105,7 +105,7 @@ py3env/
 *.nupkg
 
 .testconfig
-/*/.testconfig
+*/.testconfig
 .pytest_cache
 
 # vscode

workers/tests/endtoend/dependency_isolation_functions/report_dependencies/__init__.py

@@ -48,5 +48,4 @@ def main(req: func.HttpRequest) -> func.HttpResponse:
             "HOST_VERSION": os.getenv('HOST_VERSION')
         }
     }
-    logging.info("Dependency report: %s", json.dumps(result))
     return func.HttpResponse(json.dumps(result))