36 lines
1.1 KiB
Markdown
36 lines
1.1 KiB
Markdown
## Problem
|
|
|
|
Briefly describe the issue or feature being addressed.
|
|
|
|
## Solution
|
|
|
|
Explain your approach and any important design decisions.
|
|
|
|
## Testing
|
|
|
|
Describe how you tested the change (manual testing, automated tests,
|
|
regression tests, etc.).
|
|
|
|
- [ ] Manual Testing
|
|
- [ ] Functional Testing ([nginx-tests](https://github.com/nginx/nginx-tests))
|
|
|
|
**Closes:** #ISSUE\_NUMBER
|
|
|
|
## Checklist
|
|
|
|
Before submitting this PR, please confirm:
|
|
|
|
- [ ] I have read the [CONTRIBUTING](https://github.com/nginx/nginx/blob/master/CONTRIBUTING.md) guidelines
|
|
- [ ] I have added tests (if applicable) to validate my changes
|
|
- [ ] All existing tests pass
|
|
- [ ] I have updated documentation where necessary
|
|
- [ ] My branch is rebased on the latest master
|
|
- [ ] This PR targets the master branch from my fork
|
|
- [ ] My commit message follows NGINX standards (imperative mood, clear
|
|
subject, references related issue if applicable, and contains only
|
|
relevant changes)
|
|
|
|
## Release Notes
|
|
|
|
If this change affects users, please add a short note here describing
|
|
the impact for release documentation.
|