You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
➜ semgrep --version
1.75.0
➜ semgrep ci --help | head
SEMGREP CI(1) Semgrep ci Manual SEMGREP CI(1)
NAME
semgrep ci - the recommended way to run semgrep in CI
SYNOPSIS
semgrep ci [OPTION]… [TARGETS]…
it should be possible to pass targets to scan by semgrep however that blows up with:
➜ semgrep ci /tmp
Usage: semgrep ci [OPTIONS]
Error: Got unexpected extra argument (/tmp)
To Reproduce
➜ semgrep ci /tmp
Usage: semgrep ci [OPTIONS]
Error: Got unexpected extra argument (/tmp)
Expected behavior
Should be able to pass targets in ci subcommand, or its --help should be updated to reflect its supported capabilities.
What is the priority of the bug to you?
P0: blocking your adoption of Semgrep or workflow
P1: important to fix or quite annoying
P2: regular bug that should get fixed
Environment
If not using semgrep.dev: are you running off docker, an official binary, a local build?
Describe the bug
as per
--ci --help
it should be possible to pass targets to scan by semgrep however that blows up with:
To Reproduce
Expected behavior
Should be able to pass targets in
ci
subcommand, or its--help
should be updated to reflect its supported capabilities.What is the priority of the bug to you?
Environment
If not using semgrep.dev: are you running off docker, an official binary, a local build?
Use case
Allow to scan specific target via
semgrep ci
subcommandThe text was updated successfully, but these errors were encountered: