-
Notifications
You must be signed in to change notification settings - Fork 686
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
GitHub Issue template #1413
GitHub Issue template #1413
Conversation
@@ -0,0 +1,24 @@ | |||
name: Question |
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'd add a platform option here as well (could be optional). In many cases questions are for specific platforms
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.
added
.github/ISSUE_TEMPLATE/bug.yml
Outdated
value: | | ||
```cpp | ||
# Add a code block here, if required | ||
``` |
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.
Should we add a bug report template with specific questions people need to answer to make the bug report more structured?
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 think we already cover most of the questions that we are interested in, e.g. version, compiler, OS, etc.
Perhaps we can also add a section for backtrace, or error log, but I think these don't have to be a standalone question.
People should be able to add more information in the "description" section.
Do you have specific questions want to add to the template?
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.
Currently the bug description only includes a template for C++ code:
When I first looked at it I thought I only need to fill out the code example, and I searched where can I write the bug description 🙂
I just opened a bug in Npcap and their template is quite nice, although we need different topics:
https://github.com/nmap/npcap/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=
Maybe:
**Describe the bug**
A clear and concise description of what the bug is.
**Code example to reproduce**
(code template)
**Expected behavior**
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.
Okay, I will apply your suggestion, but I would prevent putting too many words inside, most of the time, I also ignore those "templates" when I submit issues in other projects. If we put too much stuff, people will just feel annoyed and ignore it.
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.
updated.
@seladb I guess this is ready for merge. |
@clementperon @egecetin @Dimi1010 let me know when this PR is LGTM I'll also take a look |
.github/ISSUE_TEMPLATE/black.md
Outdated
@@ -0,0 +1,6 @@ | |||
--- |
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.
Filename should black.md
or blank.md
? Maybe a typo
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.
ops, thanks!!
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.
Only left one comment. I'm not sure is a typo or not.
|
.github/ISSUE_TEMPLATE/bug.yml
Outdated
required: true | ||
- type: dropdown | ||
attributes: | ||
label: "PcapPlusPlus versions tested on:" |
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.
nit: maybe remove the :
character in the end of all labels?
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.
@seladb I followed the CPython style, but sure, let me change it.
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.
fixed.
multiple: true | ||
options: | ||
- Linux | ||
- macOS |
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.
- macOS | |
- MacOS |
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.
macOS is the correct spelling, please see https://en.wikipedia.org/wiki/MacOS
.github/ISSUE_TEMPLATE/question.yml
Outdated
If you have a question about PcapPlusPlus, please check the following resources before opening a new issue: | ||
- [PcapPlusPlus documentation](https://pcapplusplus.github.io/docs/quickstart) | ||
- [PcapPlusPlus API reference](https://pcapplusplus.github.io/docs/api) | ||
- [GIthub issues tracker](https://github.com/seladb/PcapPlusPlus/issues) |
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.
- [GIthub issues tracker](https://github.com/seladb/PcapPlusPlus/issues) | |
- [Github issues tracker](https://github.com/seladb/PcapPlusPlus/issues) |
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.
Thanks, let me correct to "GitHub", which is the correct one.
attributes: | ||
label: "Other operation systems (if applicable):" | ||
description: If you select "Other", please specify the operation system you tested on. | ||
placeholder: ex. ChromeOS, Solaris |
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.
We could also add the architecture if it's ARM64 or AMD64
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 am wondering was there any bug related to the architecture before? so far I didn't see any?
@seladb all issues addressed. please have a look. |
@tigercosmos I believe only this one is left: #1413 (comment) |
@seladb should all clear. |
@tigercosmos can you merge this branch to your fork's |
@seladb here you go.
|
Added GitHub issue template. fix #1407
The demos are as follows: