|
| 1 | +### Requirements for Contributing a Bug Fix |
| 2 | + |
| 3 | +* Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion. |
| 4 | +* The pull request must only fix an existing bug. To contribute other changes, you must use a different template. You can see all templates at https://github.com/etr/libhttpserver/tree/master/.github/PULL_REQUEST_TEMPLATE. |
| 5 | +* The pull request must update the test suite to demonstrate the changed functionality. |
| 6 | +* After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see https://github.com/etr/libhttpserver/tree/master/CONTRIBUTING.md#pull-requests. |
| 7 | + |
| 8 | +### Identify the Bug |
| 9 | + |
| 10 | +<!-- |
| 11 | +
|
| 12 | +Link to the issue describing the bug that you're fixing. |
| 13 | +
|
| 14 | +If there is not yet an issue for your bug, please open a new issue and then link to that issue in your pull request. |
| 15 | +Note: In some cases, one person's "bug" is another person's "feature." If the pull request does not address an existing issue with the "bug" label, the maintainers have the final say on whether the current behavior is a bug. |
| 16 | +
|
| 17 | +--> |
| 18 | + |
| 19 | +### Description of the Change |
| 20 | + |
| 21 | +<!-- |
| 22 | +
|
| 23 | +We must be able to understand the design of your change from this description. If we can't get a good idea of what the code will be doing from the description here, the pull request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code here recently, so please walk us through the concepts. |
| 24 | +
|
| 25 | +--> |
| 26 | + |
| 27 | +### Alternate Designs |
| 28 | + |
| 29 | +<!-- Explain what other alternates were considered and why the proposed version was selected --> |
| 30 | + |
| 31 | +### Possible Drawbacks |
| 32 | + |
| 33 | +<!-- What are the possible side-effects or negative impacts of the code change? --> |
| 34 | + |
| 35 | +### Verification Process |
| 36 | + |
| 37 | +<!-- |
| 38 | +
|
| 39 | +What process did you follow to verify that the change has not introduced any regressions? |
| 40 | +
|
| 41 | +--> |
| 42 | + |
| 43 | +### Release Notes |
| 44 | + |
| 45 | +<!-- |
| 46 | +
|
| 47 | +Please describe the changes in a single line that explains this improvement in |
| 48 | +terms that a user can understand. This text will be used in libhttpserver's release notes. |
| 49 | +
|
| 50 | +If this change is not user-facing or notable enough to be included in release notes |
| 51 | +you may use the strings "Not applicable" or "N/A" here. |
| 52 | +
|
| 53 | +Examples: |
| 54 | +
|
| 55 | +- The GitHub package now allows you to add co-authors to commits. |
| 56 | +- Fixed an issue where multiple cursors did not work in a file with a single line. |
| 57 | +- Increased the performance of searching and replacing across a whole project. |
| 58 | +
|
| 59 | +--> |
0 commit comments