-
Reason being - You have use-cases now, a template would be a good user experience.
![image](https://user-images.githubusercontent.com/61280281/147372859-3da9d9d4-2757-4a30-a6ca-597cf046b449.png)
-
-
I think we can have multiple issue templates, such as feature request, new cheat sheet, and so on.
This will be helpful for new contributors to create issues, and also there will be consistency among…
-
Should be able to save a whole issue as a template. Build it on top of the new issue URL scheme.
A File -> Templates menu should be available with saved issue templates. A management panel should be …
-
- We should consider removing the auto-applied prefixes for issue titles since the labels provide the same info
-
This causes problems:
https://psalm.dev/r/21b898850a
This is fine:
https://psalm.dev/r/a59a8c9029
-
To streamline incoming issues, we should consider using Github's functionality to use [Issue Templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-reque…
-
Currently there's only one issue template, we need more templates like feature request, question, track issue, bug report...
Examples from rust repo: https://github.com/rust-lang/rust/issues/ne…
-
Would be really nice to have issue templates that ask the user to provide their server details so we can more easily recreate when testing.
-
Should add the issue templates here as well.