Conversation
|
Nice! I'm happy to learn that it's pretty simple to setup issue templates. I'm obviously not the codeowner, but I wouldn't add so many templates as I think that too much choice will not help the user in the end. I would really only let bug and feature_request as templates as the other labels will probably be better chosen by a maintainer than a user (speeking here about feedback, unix, regression, windows, wont fix, wbt api, wbt runner). As for question, qgis_plugin, arcgis_plugin and (potentially r_package) I think those templates should not allow to open an issue but instead redirect to the appropriate website (via the config.yml file): |
|
I think Jean-Francois has very good points here. Can I ask that you revise this PR in light of these comments and resubmit? That would be appreciated. |
I removed the extra templates. redirection is not really possible. I can add a note in the templates that tells users to visit those links if their issue is related to one of those plugins? |
|
To redirect users, you just need to change the blank_issues_enabled: false
contact_links:
- name: Question
url: https://groups.google.com/g/whiteboxtools
about: >
Questions should go to the WhiteboxTools Google Group or other support forums such as https://gis.stackexchange.com/.
GitHub issues are for bug reports and suggestions for new features.See example for QGIS: |
ohh, I learned a new feature. cheers. |
Hey John,
I saw a couple of posts in g-groups around labels and templates, figured I would add some of them.
These are the first pass, however, they should be fine moving forward.
The next item I want to do is