-
Notifications
You must be signed in to change notification settings - Fork 101
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
Update issue templates #105
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.
@swapnilgm Thanks for the PR! It's a much required feature for our repo. 🙂
I just have one suggestion. PTAL.
|
||
**Expected behaviour:** | ||
A clear and concise description of what you expected to happen. | ||
|
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.
Shall we have a "Current behaviour" section to let the issue-creator tell us exactly what problem they are experiencing, as opposed to what they expected to happen..?
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.
First section i.e. Describe the bug
is exactly where issue raiser will right the current behaviour. And i don't think, we need to rename the section. @georgekuruvillak WDYT?
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.
Current behaviour is ambiguous. Describe the bug
seems better to me.
lgtm |
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.
LGTM 👍🏼
No description provided.