Add GitHub Issue templates - #5710
Merged
Merged
Conversation
pmouawad
reviewed
Sep 24, 2022
vlsi
force-pushed
the
issue_templates
branch
from
September 24, 2022 16:20
8db35d7 to
47c1877
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Configure issue templates.
Technically speaking, we could use drop-down for JMeter versions, however, it would require updating the list of versions on each release.
Here's the discussion on adding "select tag" field type in the issue form: community/community#29067, https://github.com/orgs/community/discussions/4266, so I'm inclined to keep "JMeter version" a free-text field for now.
You could preview the forms at