diff --git a/.github/label-commenter-config.yml b/.github/label-commenter-config.yml index bc0b595d..06c718b6 100644 --- a/.github/label-commenter-config.yml +++ b/.github/label-commenter-config.yml @@ -40,6 +40,36 @@ labels: pr: body: | Thanks for providing the sysinfo. Someone will be along shortly to review the PR. + + - name: hid-recorder needed + labeled: + pr: + body: | + We need some more information about your device. + Please get [hid-recorder](https://github.com/hidutils/hid-recorder) and run it against + your device. The README in that repo has more information and + instructions on how to build and run. + + Please **attach** (do not paste) the output of hid-recorder here. + unlabeled: + pr: + body: | + Thanks for providing the hid-recorder output. Someone will be along shortly to review the PR. + + - name: libinput-record needed + labeled: + pr: + body: | + We need some more information about your device. + Please run [libinput record](https://wayland.freedesktop.org/libinput/doc/latest/tools.html) + against your device **attach** (do not paste) the output here. + + `libinput record` may be in a distribution package named `libinput-utils` or `libinput-tools`. + unlabeled: + pr: + body: | + Thanks for providing the libinput record output. Someone will be along shortly to review the PR. + - name: please file pull request labeled: issue: @@ -53,3 +83,22 @@ labels: Meanwhile, I'm closing this bug in eager anticipation of a PR. action: close + + - name: autogenerated tablet file + labeled: + issue: + body: | + The data we currently have for your device has been auto-generated and is likely to be + incomplete. Please look at the corresponding `data/$vendor-$model.tablet` file in our + repository and correct the entries to the best of your abilities. + Then file a pull request with the updated entries so we can review and merge them. + + This wiki page should get you started: + https://github.com/linuxwacom/libwacom/wiki/Adding-a-new-device + + Unfortunately the maintainers have limited time and access to + hardware for testing so the best approach to get this fixed is for + you to file a pull request. + + Meanwhile, I'm closing this bug in eager anticipation of a PR. + action: close