-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add: Add a standalone plugin for checking correct file extensions #687
Conversation
Conventional Commits Report
🚀 Conventional commits found. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #687 +/- ##
==========================================
+ Coverage 78.76% 79.06% +0.30%
==========================================
Files 81 82 +1
Lines 2736 2785 +49
Branches 577 589 +12
==========================================
+ Hits 2155 2202 +47
- Misses 440 441 +1
- Partials 141 142 +1 ☔ View full report in Codecov by Sentry. |
For these we would need to have an exclusion possibility (no exclusion of
The |
Should the exclusion be for the specific file in the specific folder starting with /nasl/, or should it be a general exclusion for files with that specific name? exclusion: common/bad_dsa_ssh_host_keys.txt vs bad_dsa_ssh_host_keys.txt |
Personally i would make it as strict as possible (e.g. some one might have copied the file wrongly to e.g. common/2024):
with an option to also allow something like e.g. the following (if that is ever required to overwrite the file in different feeds) in the future:
|
Line 78 in 81f8c02
There is also an requirement to add this to the |
0c1f82f
to
792a7e8
Compare
What
Add a standalone plugin that checks that all files in a given directory and subdirectories have only valid .nasl or .inc file extensions.
Why
Files with invalid extensions make it into the feed.
Invalid: foo.nasl.nasl, foo, codespell.exclusion
Valid: foo.nasl, foo.inc
References
VTOPS-198
Checklist