2017-08-28 03:28:23 +00:00
**By submitting this pull request, I confirm the following:** `{please fill any appropriate checkboxes, e.g: [X]}`
2016-02-17 22:18:43 +00:00
2017-07-22 05:29:36 +00:00
`{Please ensure that your pull request is for the 'development' branch!}`
2016-11-04 21:01:01 +00:00
2017-09-01 00:17:08 +00:00
- [] I have read and understood the [contributors guide ](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md ), as well as this entire template.
- [] I have made only one major change in my proposed changes.
- [] I have commented my proposed changes within the code.
- [] I have tested my proposed changes, and have included unit tests where possible.
2017-06-22 19:59:07 +00:00
- [] I am willing to help maintain this change if there are issues with it later.
2017-07-22 05:29:36 +00:00
- [] I give this submission freely and claim no ownership.
2017-09-02 11:52:54 +00:00
- [] It is compatible with the [EUPL 1.2 license ](https://opensource.org/licenses/EUPL-1.1 )
- [] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
2017-12-24 01:48:15 +00:00
- [] I have Signed Off all commits. ([`git commit --signoff`](https://github.com/pi-hole/pi-hole/wiki/How-to-signoff-your-commits.))
2016-02-17 22:16:04 +00:00
2017-07-22 05:29:36 +00:00
---
2016-02-17 22:18:43 +00:00
2017-08-28 03:28:23 +00:00
**What does this PR aim to accomplish?:**
2016-02-17 22:18:43 +00:00
2017-08-28 03:28:23 +00:00
`{A detailed description, screenshots (if necessary), as well as links to any relevant GitHub issues}`
2016-10-23 22:50:59 +00:00
2017-08-28 03:28:23 +00:00
**How does this PR accomplish the above?:**
2017-07-22 05:29:36 +00:00
2017-08-28 03:28:23 +00:00
`{A detailed description (such as a changelog) and screenshots (if necessary) of the implemented fix}`
2017-07-22 05:29:36 +00:00
**What documentation changes (if any) are needed to support this PR?:**
`{A detailed list of any necessary changes}`
> * `{Please delete this quoted section when opening your pull request}`
> * You must follow the template instructions. Failure to do so will result in your issue being closed.
> * Please respect that Pi-hole is developed by volunteers, who can only reply in their spare time.
> * Detail helps us understand an issue quicker, but please ensure it's relevant.