-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Require a problem description in issues #14032
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
Conversation
Currently some issues are just code examples without a description **why** a change should be done. This leads to problems when (years later) the current behaviour is questioned and no one can remember why it was changed.
I think it may better to be added:
needs discussion though |
In Addition to the reason why the thing is actually a problem? |
See also #14031 for basically the same thing for PRs. That one also has a small example why I think such a description is needed. |
The addition seems fine to me. |
@@ -1,3 +1,7 @@ | |||
#### Problem description | |||
|
|||
[this should explain **why** the current behaviour is a problem and why the expected output is a better solution.] |
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.
what do the [ ]
do here?
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.
My idea was to indicate that this text should be replaced.
ok, let's see how this works. thanks @JanSchulz |
Currently some issues are just code examples without a description why a change should be done. This leads to problems when (years later) the current behaviour is questioned and no one can remember why it was changed.