Updating contribution guidelines#4993
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4993 +/- ##
=======================================
Coverage 80.28% 80.28%
=======================================
Files 383 383
Lines 94739 94739
=======================================
+ Hits 76060 76063 +3
+ Misses 18679 18676 -3 🚀 New features to boost your workflow:
|
7f3a82c to
c458a52
Compare
AI-Assisted: no
AI-Assisted: no
AI-Assisted: no
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi everyone !
This is a change to update the contribution guidelines for Scapy. Those are probably not final and might get updated, but we're trying to introduce some meaningful guidelines regarding the involvement of AI.
This PR:
AI-Assisted: yes/no [tool]tag on each commit. I know, it's a bit annoying, but it's probably less aggressive than having to shout at people in the PR template and the contributing guidelines. I think that for maintainers, it's a really nice approach.