[tblauvvik]

Adds an optional build-command input to the reusable CodeQL workflow, for projects that CodeQL's autobuild can't build on its own.

Why

Autobuild runs a plain build (e.g. mvn package). Some projects need extra goals. For example, a mixed Kotlin/Java module where Kotlin is compiled with an explicit kotlin:compile goal fails under autobuild with cannot find symbol, because javac runs before the Kotlin classes exist.

What changes

• New input build-command (string, default '').
• When it is set, the Autobuild step is skipped and a Build step runs the command instead. CodeQL traces the compilers it runs, as with any manual build between init and analyze.
• The command is passed through an environment variable (eval "$BUILD_COMMAND"), not interpolated into the script.
• When it is empty, nothing changes: autobuild runs as before. Existing callers are unaffected, and callers pinned to an older commit keep their current behaviour until they move their pin.

Example

    uses: OriginAS/origin-actions/.github/workflows/codeql.yml@<sha>
    with:
      jdk: 21
      build-command: mvn -B -DskipTests clean kotlin:compile compile

🤖 Generated with Claude Code