aboutsummaryrefslogtreecommitdiff
path: root/lib/mbedtls-2.27.0/.github/pull_request_template.md
diff options
context:
space:
mode:
Diffstat (limited to 'lib/mbedtls-2.27.0/.github/pull_request_template.md')
-rw-r--r--lib/mbedtls-2.27.0/.github/pull_request_template.md36
1 files changed, 0 insertions, 36 deletions
diff --git a/lib/mbedtls-2.27.0/.github/pull_request_template.md b/lib/mbedtls-2.27.0/.github/pull_request_template.md
deleted file mode 100644
index c580443..0000000
--- a/lib/mbedtls-2.27.0/.github/pull_request_template.md
+++ /dev/null
@@ -1,36 +0,0 @@
-Notes:
-* Pull requests cannot be accepted until the PR follows the [contributing guidelines](../CONTRIBUTING.md). In particular, each commit must have at least one `Signed-off-by:` line from the committer to certify that the contribution is made under the terms of the [Developer Certificate of Origin](../dco.txt).
-* This is just a template, so feel free to use/remove the unnecessary things
-## Description
-A few sentences describing the overall goals of the pull request's commits.
-
-
-## Status
-**READY/IN DEVELOPMENT/HOLD**
-
-## Requires Backporting
-When there is a bug fix, it should be backported to all maintained and supported branches.
-Changes do not have to be backported if:
-- This PR is a new feature\enhancement
-- This PR contains changes in the API. If this is true, and there is a need for the fix to be backported, the fix should be handled differently in the legacy branch
-
-Yes | NO
-Which branch?
-
-## Migrations
-If there is any API change, what's the incentive and logic for it.
-
-YES | NO
-
-## Additional comments
-Any additional information that could be of interest
-
-## Todos
-- [ ] Tests
-- [ ] Documentation
-- [ ] Changelog updated
-- [ ] Backported
-
-
-## Steps to test or reproduce
-Outline the steps to test or reproduce the PR here.