semgrep ci [targets] is not supported

[miki725]

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
• [x] 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

[romani]

@nrmancuso , what jdk syntax we support now ? 19th ? do we have full support or partial ?

[nrmancuso]

All preview and regular language features for JDK19 are supported currently.

[rnveach]

This issue should also document what we won't support, when we identify those things, like JEP 445: Unnamed Classes and Instance Main Methods .