Add Bloxstrap version to bug report Issue Form template #3357
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There’s already a checkbox for “I am using the latest version of Bloxstrap” though |
That's a fair point but people tend to ignore that. Refer to my original PR for my explanation. I still see a significant amount of issues related to an outdated version and this PR is just to be able to pinpoint specifically that. Feel free to close my PR if it isn't needed. Just putting my suggestion out there. |
|
The manual input seems like a much better way of handling this. I'll see how it goes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds an input field to the
bug_report.yamlfile for Issue Form templates for the Bloxstrap version. The goal of this PR is to better reduce issues and identify issues related to outdated versions of Bloxstrap.This might be irrelevant due to the Preliminary instructions, but a number of users still ignore such instructions and create an issue. Adding to the fact they might not be aware of not using the latest version or don't know the latest version of Bloxstrap is.
A Bloxstrap version field also adds the ability to use a GitHub Action to auto-respond to issues that have an outdated Bloxstrap version in the version field, either commenting that the version is outdated or closing the issue.