label-commenter-config.yml 6.5 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. # Reply Bot Configuration
  2. # See https://github.com/peaceiris/actions-label-commenter
  3. # Make sure to also add the response to .github/workflows/reply-bot.yml!
  4. # Due to the way it works, you have to add each response twice, once for the issue, once for the discussions!
  5. labels:
  6. #######################################################################
  7. # Bot Response: Logfile
  8. #######################################################################
  9. - name: bot-reply Logfile
  10. labeled:
  11. issue:
  12. body: |
  13. Please provide a logfile!
  14. Make sure to first enable the `DEBUG` level in `Settings->Configuration->Debug->Logfile Log Level`!
  15. Then wait until the issue arises again.
  16. When you copy the log into here, please make sure to use **Fenced code blocks** by wrapping it into separate lines with ` ``` `, see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks
  17. discussion:
  18. body: |
  19. Please provide a logfile!
  20. Make sure to first enable the `DEBUG` level in `Settings->Configuration->Debug->Logfile Log Level`!
  21. Then wait until the issue arises again.
  22. When you copy the log into here, please make sure to use **Fenced code blocks** by wrapping it into separate lines with ` ``` `, see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks
  23. #######################################################################
  24. # Bot Response: Web Console
  25. #######################################################################
  26. - name: bot-reply Web Console
  27. labeled:
  28. issue:
  29. body: |
  30. You can use the [Web Console](https://jomjol.github.io/AI-on-the-edge-device/index.html) to get USB log from the device.
  31. The USB log contains more information about the startup and operation of the device than the normal Web UI log
  32. When you copy the log into herm, please make sure to use **Fenced code blocks** by wrapping it into separate lines with ` ``` `, see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks
  33. discussion:
  34. body: |
  35. You can use the [Web Console](https://jomjol.github.io/AI-on-the-edge-device/index.html) to get USB log from the device.
  36. The USB log contains more information about the startup and operation of the device than the normal Web UI log
  37. When you copy the log into herm, please make sure to use **Fenced code blocks** by wrapping it into separate lines with ` ``` `, see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks
  38. #######################################################################
  39. # Bot Response: Properly Format Code
  40. #######################################################################
  41. - name: bot-reply Properly Format Code
  42. labeled:
  43. issue:
  44. body: |
  45. Please make sure to use **Fenced code blocks** by wrapping it into separate lines with ` ``` `, see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks
  46. This makes your code or log much easier to read!
  47. discussion:
  48. body: |
  49. Please make sure to use **Fenced code blocks** by wrapping it into separate lines with ` ``` `, see https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks#fenced-code-blocks
  50. This makes your code or log much easier to read!
  51. #######################################################################
  52. # Bot Response: Web Installer
  53. #######################################################################
  54. - name: bot-reply Web Installer
  55. labeled:
  56. issue:
  57. body: |
  58. You can use the [Web Installer](https://jomjol.github.io/AI-on-the-edge-device/index.html) install the firmware onto the ESP32.
  59. discussion:
  60. body: |
  61. You can use the [Web Installer](https://jomjol.github.io/AI-on-the-edge-device/index.html) install the firmware onto the ESP32.
  62. #######################################################################
  63. # Bot Response: Rolling Build
  64. #######################################################################
  65. - name: bot-reply Rolling Build
  66. labeled:
  67. issue:
  68. body: |
  69. You can try the latest [Automatic Build](https://github.com/jomjol/AI-on-the-edge-device/actions/workflows/build.yaml?query=branch%3Arolling+event%3Apush) of the the `rolling` or any other branch. It might already contain a fix for your issue.
  70. See the [documentation](https://jomjol.github.io/AI-on-the-edge-device-docs/rolling-installation) for additional information.
  71. discussion:
  72. body: |
  73. You can try the latest [Automatic Build](https://github.com/jomjol/AI-on-the-edge-device/actions/workflows/build.yaml?query=branch%3Arolling+event%3Apush) of the the `rolling` or any other branch. It might already contain a fix for your issue.
  74. See the [documentation](https://jomjol.github.io/AI-on-the-edge-device-docs/rolling-installation) for additional information.
  75. #######################################################################
  76. # Bot Response: Show Trained Digits/Pointers
  77. #######################################################################
  78. - name: bot-reply Show Trained Digits/Pointers
  79. labeled:
  80. issue:
  81. body: |
  82. See [Digital Digits](https://jomjol.github.io/neural-network-digital-counter-readout) resp. [Analogue Pointers](https://jomjol.github.io/neural-network-analog-needle-readout) for an overview of all trained data.
  83. If your type is not contained it can be added to our training material, see [here](https://jomjol.github.io/AI-on-the-edge-device-docs/collect-new-images/).
  84. discussion:
  85. body: |
  86. See [Digital Digits](https://jomjol.github.io/neural-network-digital-counter-readout) resp. [Analogue Pointers](https://jomjol.github.io/neural-network-analog-needle-readout) for an overview of all trained data.
  87. If your type is not contained it can be added to our training material, see [here](https://jomjol.github.io/AI-on-the-edge-device-docs/collect-new-images/).