🐛 --staged throws an error if no files affected

[apetta]

Environment information

CLI:
  Version:                      1.9.4
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v23.6.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/10.2.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

Running cli commands w/ --staged throws an error if biome does not have any files to look at. This is problematic when using biome in a pre-commit hook w/ changes to files that biome doesn't format/lint (excluded through config).

See example output:

//:check: > biome check . --staged
//:check: 
//:check: Checked 0 files in 116µs. No fixes applied.
//:check: internalError/io ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
//:check: 
//:check:   × No files were processed in the specified paths.
//:check:   
//:check: 
//:check:  ELIFECYCLE  Command failed with exit code 1.

Expected result

It should not throw an error, and instead resolve successfully even if no files are affected.

Code of Conduct

• I agree to follow Biome's Code of Conduct

[apetta]

--no-errors-on-unmatched is what I'm after