mirror of
https://github.com/pi-hole/pi-hole.git
synced 2024-11-15 02:42:58 +00:00
Remove respository templates.
Use org templates instead. Signed-off-by: Dan Schaper <dan.schaper@pi-hole.net>
This commit is contained in:
parent
48820d181c
commit
8fa9096508
2 changed files with 0 additions and 68 deletions
37
.github/ISSUE_TEMPLATE.md
vendored
37
.github/ISSUE_TEMPLATE.md
vendored
|
@ -1,37 +0,0 @@
|
||||||
**In raising this issue, I confirm the following:** `{please fill the checkboxes, e.g: [X]}`
|
|
||||||
|
|
||||||
- [] I have read and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md).
|
|
||||||
- [] The issue I am reporting can be *replicated*.
|
|
||||||
- [] The issue I am reporting isn't a duplicate (see [FAQs](https://github.com/pi-hole/pi-hole/wiki/FAQs), [closed issues](https://github.com/pi-hole/pi-hole/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), and [open issues](https://github.com/pi-hole/pi-hole/issues)).
|
|
||||||
|
|
||||||
**How familiar are you with the the source code relevant to this issue?:**
|
|
||||||
|
|
||||||
`{Replace this with a number from 1 to 10. 1 being not familiar, and 10 being very familiar}`
|
|
||||||
|
|
||||||
---
|
|
||||||
**Expected behavior:**
|
|
||||||
|
|
||||||
`{A detailed description of what you expect to see}`
|
|
||||||
|
|
||||||
**Actual behavior:**
|
|
||||||
|
|
||||||
`{A detailed description and/or screenshots of what you do see}`
|
|
||||||
|
|
||||||
**Steps to reproduce:**
|
|
||||||
|
|
||||||
`{Detailed steps of how we can reproduce this}`
|
|
||||||
|
|
||||||
**Debug token provided by [uploading `pihole -d` log](https://discourse.pi-hole.net/t/the-pihole-command-with-examples/738#debug):**
|
|
||||||
|
|
||||||
`{Alphanumeric token}`
|
|
||||||
|
|
||||||
**Troubleshooting undertaken, and/or other relevant information:**
|
|
||||||
|
|
||||||
`{Steps of what you have done to fix this}`
|
|
||||||
|
|
||||||
> * `{Please delete this quoted section when opening your issue}`
|
|
||||||
> * You must follow the template instructions. Failure to do so will result in your issue being closed.
|
|
||||||
> * Please [submit any feature requests here](https://discourse.pi-hole.net/c/feature-requests), so it is votable and trackable by the community.
|
|
||||||
> * Please respect that Pi-hole is developed by volunteers, who can only reply in their spare time.
|
|
||||||
> * Detail helps us understand and resolve an issue quicker, but please ensure it's relevant.
|
|
||||||
> * _This template was created based on the work of [`udemy-dl`](https://github.com/nishad/udemy-dl/blob/master/LICENSE)._
|
|
31
.github/PULL_REQUEST_TEMPLATE.md
vendored
31
.github/PULL_REQUEST_TEMPLATE.md
vendored
|
@ -1,31 +0,0 @@
|
||||||
**By submitting this pull request, I confirm the following:**
|
|
||||||
*please fill any appropriate checkboxes, e.g: [X]*
|
|
||||||
|
|
||||||
- [ ] 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.
|
|
||||||
- [ ] I am willing to help maintain this change if there are issues with it later.
|
|
||||||
- [ ] I give this submission freely and claim no ownership.
|
|
||||||
- [ ] 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))
|
|
||||||
|
|
||||||
Please make sure you [Sign Off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/contributing/).
|
|
||||||
|
|
||||||
---
|
|
||||||
**What does this PR aim to accomplish?:**
|
|
||||||
*A detailed description, screenshots (if necessary), as well as links to any relevant GitHub issues*
|
|
||||||
|
|
||||||
|
|
||||||
**How does this PR accomplish the above?:**
|
|
||||||
*A detailed description (such as a changelog) and screenshots (if necessary) of the implemented fix*
|
|
||||||
|
|
||||||
|
|
||||||
**What documentation changes (if any) are needed to support this PR?:**
|
|
||||||
*A detailed list of any necessary changes*
|
|
||||||
|
|
||||||
|
|
||||||
---
|
|
||||||
* You must follow the template instructions. Failure to do so will result in your pull request being closed.
|
|
||||||
* Please respect that Pi-hole is developed by volunteers, who can only reply in their spare time.
|
|
||||||
|
|
Loading…
Reference in a new issue