Brendon Go

You can probably reproduce this by creating an empty archive file and running `bento check` on some staged changes (and there are findings that would occur if `bento check --all`...

Reproducing: ``` git clone https://github.com/pallets/flask git checkout 38eb5d3b49d628785a470e2e773fc5ac82e3c8e4 bento init echo "\n" >> tests/test_templating.py git add tests/test_templating.py bento check ``` Prints out ``` ✔ 0 findings due to staged changes...

Would it make sense to recommend `bento archive --all` in the text of `bento check --all`

@CAM-Gerlach yeah there's some magic going on under the hood that automatically does diff aware mode if the triggering event is a pull-request in github actions. You should be able...


+1 on the workaround for now I think the reason we have it the current way (an extension we don't have coded into semgrep (say .foo) is treated as unknown...

Internally the --lang is used the same way as the language field in a rule.yaml (--pattern and --lang actually just help us create a yaml file then we handle it...

@bocajspear1 can you give us an example code and rules to reproduce?

Hi! An exit code of 7 https://semgrep.dev/docs/cli-reference/#:~:text=7%3A%20At%20least%20one%20rule%20in%20configuration%20is%20invalid. probably means one of the rules you are running has invalid syntax.

Are the configuration options in the `semgrep scan --help` text insufficient? I disagree that the error message of an improper usage needs to tell the user how to use a...