Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

semgrep ci [targets] is not supported #10305

Open
1 of 3 tasks
miki725 opened this issue Jun 4, 2024 · 0 comments
Open
1 of 3 tasks

semgrep ci [targets] is not supported #10305

miki725 opened this issue Jun 4, 2024 · 0 comments

Comments

@miki725
Copy link

miki725 commented Jun 4, 2024

Describe the bug

as per --ci --help

➜ 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?

➜ semgrep --version
1.75.0

➜ pipx list | grep semgrep
   package semgrep 1.75.0, installed using Python 3.12.3
    - pysemgrep
    - semgrep

Use case

Allow to scan specific target via semgrep ci subcommand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant