mirror of
https://github.com/caddyserver/caddy.git
synced 2025-01-16 15:56:28 +03:00
41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
|
---
|
||
|
|
name: Pull request
|
||
|
|
about: Propose changes to the code
|
||
|
|
title: ''
|
||
|
|
labels: ''
|
||
|
|
assignees: ''
|
||
|
|
---
|
||
|
|
|
||
|
|
<!--
|
||
|
|
Thank you for contributing to Caddy! Please fill this out to help us make the most of your pull request.
|
||
|
|
|
||
|
|
Was this change discussed in an issue first? That can help save time in case the change is not a good fit for the project. Not all pull requests get merged.
|
||
|
|
|
||
|
|
It is not uncommon for pull requests to go through several, iterative reviews. Please be patient with us! Every reviewer is a volunteer, and each has their own style.
|
||
|
|
-->
|
||
|
|
|
||
|
|
## 1. What does this change do, exactly?
|
||
|
|
<!-- Please be specific. Motivate the problem, and justify why this is the best solution. -->
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
## 2. Please link to the relevant issues.
|
||
|
|
<!-- This adds crucial context to your change. -->
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
## 3. Which documentation changes (if any) need to be made because of this PR?
|
||
|
|
<!-- Reviewers will often reference this first in order to know what to expect from the change. Please be specific enough so that they can paste your wording into the documentation directly. -->
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
## 4. Checklist
|
||
|
|
|
||
|
|
- [ ] I have written tests and verified that they fail without my change
|
||
|
|
- [ ] I have squashed any insignificant commits
|
||
|
|
- [ ] This change has comments explaining package types, values, functions, and non-obvious lines of code
|
||
|
|
- [ ] I am willing to help maintain this change if there are issues with it later
|