Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,20 @@
<!-- This is just a checklist to guide you. Please remove it if you check all items. -->
<!-- This is a checklist of actions required to have a PR reviewed. You should include it and fill it accordingly. (You may only remove it if you check all items and you are a well-known contributor.) -->

**Checklist:**
**Checklist :**

- [ ] If you are new to Scapy: I have checked [CONTRIBUTING.md](https://github.com/secdev/scapy/blob/master/CONTRIBUTING.md) (esp. section submitting-pull-requests)
- [ ] I squashed commits belonging together
- [ ] I added unit tests or explained why they are not relevant
- [ ] I executed the regression tests (using `tox`)
- [ ] If the PR is still not finished, please create a [Draft Pull Request](https://github.blog/2019-02-14-introducing-draft-pull-requests/)
- [ ] This PR uses (partially) AI-generated code. If so:
- [ ] I ensured the generated code follows the internal concepts of scapy
- [ ] This PR has a test coverage > 90%
- [ ] I reviewed every generated line
- [ ] If this PR contains more than 500 lines of code (excluding unit tests) I considered splitting this PR.
- [ ] I considered interoperability tests with existing packages or utilities to ensure conformity of a newly generated protocol

**I understand that failing to mention the use of AI may result in a ban. (We do not forbid it, but you must play fair. Be warned !)**

<!-- brief description what this PR will do, e.g. fixes broken dissection of XXX -->

Expand Down
Loading