chore: switch to more detailed yml based bug report template #352
Conversation
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
✅ Deploy Preview for netlify-plugin-gatsby-demo canceled.
|
ascorbic
reviewed
Apr 12, 2022
ascorbic
reviewed
Apr 12, 2022
Co-authored-by: Matt Kane <m@mk.gg>
ericapisani
approved these changes
Apr 19, 2022
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.
Which problem is this pull request solving?
Switching to a form based bug report template. Allows us to get more information from bug reports, allowing us to reproduce them more easily for fixes.
Describe the solution you've chosen
I've used the same outline that we're using in the nextjs plugin bug report, but customized it for gatsby - referencing the old bug report template.
Checklist
Please add a
xinside each checkbox:README.md, thedocsdirectory (ifany) and the
examplesdirectory (if any).seen below.