|
1 | | -<!--- Provide a general summary of your changes in the Title above --> |
| 1 | +<!-- Once the Pull Request is created, do not forget to: |
| 2 | +1. Link issues to the PR if available |
| 3 | +2. Mention dappnode core members |
| 4 | +3. Add proper labels |
| 5 | +--> |
2 | 6 |
|
3 | | -[linuxserverurl]: https://linuxserver.io |
4 | | -[][linuxserverurl] |
| 7 | +**What type of PR is this?** |
5 | 8 |
|
| 9 | +> Uncomment one line below and remove others. |
| 10 | +> |
| 11 | +> Bug fix |
| 12 | +> Feature |
| 13 | +> Documentation |
| 14 | +> Other |
6 | 15 |
|
7 | | -<!--- Before submitting a pull request please check the following --> |
| 16 | +**What does this PR do? Why is it needed?** |
8 | 17 |
|
9 | | -<!--- If this is a fix for a typo in code or documentation in the README please file an issue and let us sort it out we do not need a PR --> |
10 | | -<!--- Ask yourself if this modification is something the whole userbase will benefit from, if this is a specific change for corner case functionality or plugins please look at making a Docker Mod or local script https://blog.linuxserver.io/2019/09/14/customizing-our-containers/ --> |
11 | | -<!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message --> |
12 | | -<!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message --> |
13 | | -<!--- We maintain a changelog of major revisions to the container at the end of readme-vars.yml in the root of this repository, please add your changes there if appropriate --> |
| 18 | +**How can be tested?** |
14 | 19 |
|
| 20 | +> Provide well detailed instructions to test this PR |
15 | 21 |
|
16 | | -<!--- Coding guidelines: --> |
17 | | -<!--- 1. Installed packages in the Dockerfiles should be in alphabetical order --> |
18 | | -<!--- 2. Changes to Dockerfile should be replicated in Dockerfile.armhf and Dockerfile.aarch64 if applicable --> |
19 | | -<!--- 3. Indentation style (tabs vs 4 spaces vs 1 space) should match the rest of the document --> |
20 | | -<!--- 4. Readme is auto generated from readme-vars.yml, make your changes there --> |
21 | | - |
22 | | ------------------------------- |
23 | | - |
24 | | - - [ ] I have read the [contributing](https://github.com/linuxserver/docker-wireguard/blob/master/.github/CONTRIBUTING.md) guideline and understand that I have made the correct modifications |
25 | | - |
26 | | ------------------------------- |
27 | | - |
28 | | -<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. --> |
29 | | - |
30 | | -## Description: |
31 | | -<!--- Describe your changes in detail --> |
32 | | - |
33 | | -## Benefits of this PR and context: |
34 | | -<!--- Please explain why we should accept this PR. If this fixes an outstanding bug, please reference the issue # --> |
35 | | - |
36 | | -## How Has This Been Tested? |
37 | | -<!--- Please describe in detail how you tested your changes. --> |
38 | | -<!--- Include details of your testing environment, and the tests you ran to --> |
39 | | -<!--- see how your change affects other areas of the code, etc. --> |
40 | | - |
41 | | - |
42 | | -## Source / References: |
43 | | -<!--- Please include any forum posts/github links relevant to the PR --> |
| 22 | +**Other notes for review** |
0 commit comments