summaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE/other_issues.yml
diff options
context:
space:
mode:
authorNick Brassel <nick@tzarc.org>2023-02-03 07:14:26 +1100
committerGitHub <noreply@github.com>2023-02-03 07:14:26 +1100
commiteeadbd217661c07852b8906ce038415f36961f4e (patch)
tree36236a6b308fd407d25ed8068bd09438c73c5429 /.github/ISSUE_TEMPLATE/other_issues.yml
parentf7e69639b5bb3333d58b6da5df28ffcc59931bb8 (diff)
Politely ask people not to submit issues to add support for unknown keyboards. (#19737)
Diffstat (limited to '.github/ISSUE_TEMPLATE/other_issues.yml')
-rw-r--r--.github/ISSUE_TEMPLATE/other_issues.yml5
1 files changed, 4 insertions, 1 deletions
diff --git a/.github/ISSUE_TEMPLATE/other_issues.yml b/.github/ISSUE_TEMPLATE/other_issues.yml
index 7c4fbeb23c..d3a890e45d 100644
--- a/.github/ISSUE_TEMPLATE/other_issues.yml
+++ b/.github/ISSUE_TEMPLATE/other_issues.yml
@@ -10,7 +10,10 @@ body:
attributes:
value: |
Please check [https://docs.qmk.fm/#/support](https://docs.qmk.fm/#/support) for additional resources first. If that doesn't answer your question, choose the bug report template instead, as that may be more appropriate.
+
+ Please refrain from asking maintainers to add support for specific keyboards -- it is unlikely they will have hardware available, and will not be able to help.
+ Your best bet is to take the initiative, add support, then submit a PR yourself.
- type: textarea
attributes:
label: Issue Description
- description: Describe your issue in as much detail as possible. \ No newline at end of file
+ description: Describe your issue in as much detail as possible.