Skip to content
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

Merged
merged 25 commits into from
Jun 2, 2024
Merged

GitHub Issue template #1413

merged 25 commits into from
Jun 2, 2024

Conversation

tigercosmos
Copy link
Collaborator

@tigercosmos tigercosmos commented May 29, 2024

Added GitHub issue template. fix #1407

The demos are as follows:

image

image

@tigercosmos tigercosmos requested a review from seladb as a code owner May 29, 2024 06:45
@tigercosmos tigercosmos changed the base branch from master to dev May 29, 2024 06:47
@@ -0,0 +1,24 @@
name: Question
Copy link
Owner

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

Comment on lines 29 to 32
value: |
```cpp
# Add a code block here, if required
```
Copy link
Owner

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?

Copy link
Collaborator Author

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?

Copy link
Owner

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:
image

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated.

@tigercosmos
Copy link
Collaborator Author

@seladb I guess this is ready for merge.

@seladb
Copy link
Owner

seladb commented May 30, 2024

@clementperon @egecetin @Dimi1010 let me know when this PR is LGTM

I'll also take a look

@seladb seladb requested review from Dimi1010 and egecetin May 30, 2024 07:38
@@ -0,0 +1,6 @@
---
Copy link
Collaborator

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

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ops, thanks!!

Copy link
Collaborator

@egecetin egecetin left a 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.

@tigercosmos tigercosmos requested a review from seladb May 30, 2024 08:11
@Dimi1010
Copy link
Collaborator

@tigercosmos can you merge https://github.com/tigercosmos/PcapPlusPlus/tree/issue_template to https://github.com/tigercosmos/PcapPlusPlus/tree/master so it'll be easier to test the different issues types?

done, you can check now

The bug report template has an issue
image

required: true
- type: dropdown
attributes:
label: "PcapPlusPlus versions tested on:"
Copy link
Owner

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?

Copy link
Collaborator Author

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.

Copy link
Collaborator Author

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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- macOS
- MacOS

Copy link
Collaborator Author

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

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)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [GIthub issues tracker](https://github.com/seladb/PcapPlusPlus/issues)
- [Github issues tracker](https://github.com/seladb/PcapPlusPlus/issues)

Copy link
Collaborator Author

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
Copy link
Collaborator

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

Copy link
Collaborator Author

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?

@tigercosmos tigercosmos requested a review from seladb May 31, 2024 01:11
@tigercosmos
Copy link
Collaborator Author

@seladb all issues addressed. please have a look.

@tigercosmos tigercosmos enabled auto-merge (squash) May 31, 2024 04:56
@seladb
Copy link
Owner

seladb commented May 31, 2024

@tigercosmos I believe only this one is left: #1413 (comment)

@tigercosmos
Copy link
Collaborator Author

@seladb should all clear.

@seladb
Copy link
Owner

seladb commented May 31, 2024

@seladb should all clear.

@tigercosmos can you merge this branch to your fork's master branch so I can review it one last time?

@tigercosmos
Copy link
Collaborator Author

@seladb here you go.

@seladb should all clear.

@tigercosmos can you merge this branch to your fork's master branch so I can review it one last time?

@tigercosmos tigercosmos merged commit da1ef60 into seladb:dev Jun 2, 2024
39 checks passed
@tigercosmos tigercosmos deleted the issue_template branch June 2, 2024 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Introduce GitHub issue template
5 participants