-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce GitHub issue template for reporting a bug #223
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some suggestions, the rest looks good to me!
Suggested commit message:
We could decide to drop |
b3708ce
to
77ec08d
Compare
a47b2bc
to
e686b3b
Compare
Co-authored-by: Rick Ossendrijver <[email protected]>
d02025d
to
ab8d97b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I rebased and added a commit with some extra details. I also simplified some of the sentences (avoiding "implicit words"), as that might make the template more accessible to non-native speakers.
Once we make the repo public we could perhaps also try the issue forms beta
Super, thanks @Stephan202. The good thing of the issue forms are that they are quite rigid, the bad thing is that they are ... quite rigid. Let's start with the current template to verify if this setup works for our users. |
No description provided.