chore: Replace markdown issue templates with forms #938
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.
Related issue(s)
Resolves #
Description
This switches our markdown issue templates into GitHub Issue Forms. I like these issue forms because we can provide a lot of extra information to submitters that isn't leaked into the issue body, and we don't need to use comments.
You can test the organization-wide generic ones at https://github.com/noir-lang/aztec_backend/issues/new?assignees=&labels=bug&template=bug_report.yml and these will also render as forms if you look at the markdown directly on my branch (not in the diff).
I've kept these templates in the repository and updated them because they capture more specific information about the environment. When you override a single issue template in the repository, you need to provide them all, so the feature_request.yml is the same as the company wide one.
Copying @Globallager since he last made updates to the environment section.
Summary of changes
Dependency additions / changes
Test additions / changes
Checklist
cargo fmt
with default settings.Additional context