chore: issue forms with reason-listings #3476
Conversation
CommanderStorm
changed the title
| value: | | ||
| * SQLx version: [REQUIRED] | ||
| * SQLx features enabled: [REQUIRED] | ||
| * Database server and version: [REQUIRED] (MySQL / Postgres / SQLite <x.y.z>) | ||
| * Operating system: [REQUIRED] | ||
| * `rustc --version`: [REQUIRED] |
There was a problem hiding this comment.
Might as well break these out into separate fields.
There was a problem hiding this comment.
Fair enough.
This has the downside of looking a bit longer in the issue that is genereated, but that is likely an ok downside
| attributes: | ||
| label: Additional Context | ||
| description: Add any other context or screenshots about the feature request here | ||
| placeholder: ... |
There was a problem hiding this comment.
What maybe would be nice is a field where they list some relevant areas (e.g. mysql, postgres, macros, etc).
Also, "is this a breaking change? why or why not?"
There was a problem hiding this comment.
unsure about the wording on this one. We maybe need to iterate on the wording a bit.
What kind of answers would you like to this question?
There was a problem hiding this comment.
And should this field be mandatory?
|
Being upfront: Sorry, hope that does not bother you too much |
Co-authored-by: Austin Bonander <[email protected]>
Co-authored-by: Austin Bonander <[email protected]>
Does your PR solve an issue?
As discussed in #3471, I have added a field to the form.
I have also migrated to using issue-forms as they are a bit better too fill out and users are less likely to flat-out ignore the form.
You can preview it here: