semgrep
Remote docker container runs conflict
bento-action doesn't work with 0.11.1 on PRs, probably because it tries to create docker containers with the same name twice, for the two scans on committed and staged code.
@nbrahms suggested we should always create a new container.
@underyx I thought we packaged semgrep now as a binary to side-step a dependency on Docker for the GitHub Action?
@nbrahms @DrewDennison What's the roadmap for deprecating semgrep-lint Action and/or merging it + Bento Action?
oh, it does work, but it was for the bento-registry docker command
@nbrahms said that dockerfile should land in 0.12, not 0.11 — so this path forward here would be to make bento-action use the headless bento release, which does have a dockerfile