Replies: 4 comments
-
I think it would be a good idea. I was also thinking the issue template could use some improvement. For example, it says to post screenshots so people end up posting a screenshot of the problematic code, which I think is worse than copy paste as it forces you to re-type it. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
Ahh, cool, I see that github supports constructing issue forms using YAML. I would propose that we give that a try when replacing the issue template. Then we can provide clear descriptions to explain the different fields. I think it could save a lot of time to require a minimal reproducible example for issues. But not everyone knows what this means, or why it's important. So I'm thinking our contributing guidelines could include information about this. And to save on writing the same stuff over and over again, perhaps we could add a bot that posts a standard explanation if we add a certain tag (e.g. "Needs reproduction") to an issue? That workflow would also make it easier to see at a glance which issues need attention, and which ones are awaiting more information from the user. |
Beta Was this translation helpful? Give feedback.
-
Note to self... should probably also ask for the output of |
Beta Was this translation helpful? Give feedback.
-
Could it be worth having a pull request template to help encourage/guide submitters to follow guidelines and provide relevant information?
I made a suggestion/example but thought I would ask for feedback before submitting a PR
Beta Was this translation helpful? Give feedback.
All reactions