Brendon Go

Oh I see. So it's less the improper usage getting instructions and more plain usage without any flags getting instructions.

To get this to work we need to deprecate `semgrep` being an alias for `semgrep scan`

I checked the reproduction and it looks like this is no longer an issue

IMO correct behavior here might be to exit with an error for having multiple rules with the same id

Relevant PR potentially: https://github.com/returntocorp/semgrep/pull/3173/files

I think this reveals a larger feature gap that the includes/excludes actually cannot target a single file in the top level without also acting as a wildcard for other files...

FYI we do not support semgrep running on Windows. WSL should just work

@BobbyTRU did you manage to get this working on WSL?

I was unable to reproduce this but I think it might be because the USER used to download the semgrep repo and the USER inside the docker context don't quite...

@zakrush as a workaround for now can you just `mkdir semgrep-core/src/ocaml-tree-sitter-core/downloads` before running `docker build .`?