docs: add issue and pull request preflight checklists to reduce administrative overhead during issue and pull request review

This commit is contained in:
nekename committed 2026-02-19 21:54:35 +00:00
1 parent ea0619db71
commit 0a7d0cf636
3 files changed
+34

No files matched your search

+14
View File
@@ -0,0 +1,14 @@
---
name: "Bug report"
about: "Create a report to help us improve"
labels: "bug"
---
**Preflight checklist**
- [ ] I have searched the existing issues and believe this will not be a duplicate of any existing issue.
- [ ] I understand that if this issue is about support for non-Elgato or non-Tacto hardware, it will be closed without explanation, as per issue #38, and that it should be raised in the repository of the plugin that provides support for the hardware.
- [ ] I will provide the OpenDeck log file and the log files of plugins involved, where applicable.
- [ ] I will provide my operating system information and method of installation, as well as any steps I have taken to troubleshoot the issue.
- [ ] I certify that I am using the latest available version of OpenDeck, and that I will provide enough information to reproduce the issue.
---
+13
View File
@@ -0,0 +1,13 @@
---
name: "Feature request"
about: "Suggest an idea for this project"
labels: "enhancement"
---
**Preflight checklist**
- [ ] I have searched the existing issues and believe this will not be a duplicate of any existing issue.
- [ ] I understand that if this issue is about support for non-Elgato or non-Tacto hardware, it will be closed without explanation, as per issue #38.
- [ ] I understand that requests for the creation of new plugins or implementation of new actions should be opened as Discussions, not Issues.
- [ ] I reasonably believe that the time required to implement this feature is proportional to the value it will provide to users.
---
+7
View File
@@ -0,0 +1,7 @@
**Preflight checklist**
- [ ] I understand that if this pull request is about support for non-Elgato or non-Tacto hardware, it will be closed without explanation, as per issue #38.
- [ ] I have ensured that I have run the appropriate formatter on my changes and that my code produces no linter violations.
- [ ] I have thoroughly reviewed the diff of my changes and ensured that I have neither introduced any unrelated additions, nor differences in unmodified code.
- [ ] I will keep "Allow edits from maintainers" enabled for this pull request.
---