diff options
| author | lokher <lokher@gmail.com> | 2023-04-26 16:32:15 +0800 |
|---|---|---|
| committer | lokher <lokher@gmail.com> | 2023-04-26 16:32:15 +0800 |
| commit | e4f4ceaf3f2e3d25fb282273a81f9b58790fc427 (patch) | |
| tree | c0a257eab0ffe5238fdf2c04882e8ee1fe8fc46e /.github/ISSUE_TEMPLATE/other_issues.yml | |
| parent | 103badc87cb50db1ff3851c84331e86ba78fb681 (diff) | |
merge upstream 713427c
Diffstat (limited to '.github/ISSUE_TEMPLATE/other_issues.yml')
| -rw-r--r-- | .github/ISSUE_TEMPLATE/other_issues.yml | 5 |
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. |