New bug report and feature request templates #801
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub recently introduced a new way of setting up issue reporting forms, with more controls and the possibility to add additional instructions for bug reporters.
This PR replaces the existing two old Markdown templates with four new report forms:
All report forms have a header which tells reporters that we won't accept any issues about the Android apps in the play store, with a checkbox that must be ticked where the user acknowledges this. This will surely not prevent people from ticking the box and creating an issue for the app anyway, but we can then close it without any further comment or discussion.
All other repos in the projectM org on GitHub will receive a config.yml in their issue template dir, which will disable the empty report link at the bottom and add a link that redirects to this repo here. We can then triage new reports and move them to the correct repository, without requiring the reporter to check in advance where the issue actually belongs.