-
Notifications
You must be signed in to change notification settings - Fork 602
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
Allow choosing rules based on severity #1509
Labels
Comments
Closed by #2133. Available in Semgrep 0.33.0 |
IagoAbal
pushed a commit
that referenced
this issue
May 14, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 14, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 14, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
Closed
IagoAbal
pushed a commit
that referenced
this issue
May 14, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 15, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 15, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 15, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 15, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
IagoAbal
pushed a commit
that referenced
this issue
May 15, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
aryx
added a commit
that referenced
this issue
May 15, 2024
test plan: modify OSS/src/main/Main.ml indentation and run pre-commit run -a => now it fixes the file synced from 0fb525f415fcc7bfe13cda0e0c0b9b1bd86c090b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
This would allow a user to choose which rule severity -
ERROR
,WARNING
orINFO
they would like to report findings on. For example, a user would only want to report findings that have severityERROR
. This could be added as an optional command line argument that can be configured by the user. By default, semgrep would use all the rules regardless of the severity rating.Without this option, users would have to manually discard and re-add rules with a certain severity they do not/do want to report.
I imagine the outcome of this so be allowing a parameter called
severity
that could take different values such as:semgrep --severity ERROR ...
to only report bugs called by rules which have the severityERROR
The text was updated successfully, but these errors were encountered: