Luke O'Malley

It may be as simple as making this modification: ```bash ⚠ Nothing to check or archive. Please confirm that changes are staged and not excluded by `.bentoignore`. To check all...

@dmontagu Thank you for the feedback, as always. Does the following command solve your issue? ```shell $ bento check --no-pager ``` @nbrahms Is there an environment variable or setting to...

@nbrahms Going to change the title back. I think @dmontagu's `--help` point is a good one, but isn't the core of the issue (I've opened a seperate issue to address...

@nbrahms Updating the title again. I'm comfortable with the default behavior, and like your suggestion that this is globally configurable.

This is still happening and caused confusion during a debug session yesterday. The main issue for me is that check-ids like `parse-error` are returned and users don't know what that...

@underyx Is this issue present in Semgrep and/or something we need to consider as we port diff-awareness?

@DrewDennison @aryx Thoughts on where/when to prioritize this work?

Re-opening after discussion with vamsi on the Semgrep Slack #general channel ([here](https://r2c-community.slack.com/archives/CK86BJ5DW/p1627325715074900)).

CC @ajinabraham who maintains nodejsscan.

Hey @benjaminch! Semgrep maintainer here. @dgryski's rules are also published to the Semgrep registry if you'd like to skip the `curl`: ```bash semgrep --config http://semgrep.dev/r/dgryski.semgrep-go ``` This is the equivalent...