Update issue forms #426
Merged
Update issue forms #426
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
|
@Andrea-Havron-NOAA (or anyone else) Feel free to suggest changes or push them directly to the branch. |
Andrea-Havron-NOAA
approved these changes
Jul 21, 2023
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.
What is the feature?
Streamline issue forms (addresses #406 ), as discussed at the FIMS seaside chat.
How have you implemented the solution?
edited the yaml files to change the formatting
Does the PR impact any other area of the project?
No
How to test this change
Check out the issue options after pushing to main to verify they change (if not, we may have a YAML syntax problem, but I'm not sure how to test this on a branch)
Developer pre-PR checklist