README documents use-bazel, but the action input is use_bazel — Bazel mode silently not enabled #102

Summary

The README's configuration table documents the Bazel toggle as use-bazel (hyphenated), but action.yml declares the input as use_bazel (snake_case) and src/scan.ts reads it via core.getBooleanInput("use_bazel").

Impact

GitHub Actions resolves step inputs by uppercasing the with: key and converting spaces to underscores — hyphens are preserved. So a workflow that follows the README:

- uses: endorlabs/github-action@v1
  with:
    namespace: example
    use-bazel: true        # per README

sets INPUT_USE-BAZEL, which the action never reads. Bazel mode is therefore silently disabled and the scan runs as a non-Bazel scan. The only signal is an easily-missed "Unexpected input(s) 'use-bazel'" annotation on the workflow run — nothing fails.

All other Bazel inputs (bazel_targets_query, bazel_include_targets, bazel_exclude_targets) are snake_case in both the README and action.yml; use-bazel appears to be a one-off typo.

Suggested fix

Correct the README to use_bazel, or declare a hyphenated alias in action.yml and read both in code for backwards compatibility.

References (v1.1.13, commit f46ffb0)

• README.md — scanning parameters table, use-bazel row
• action.yml — use_bazel: input declaration
• src/scan.ts — core.getBooleanInput("use_bazel")