Stabilize CMake GitHub Actions by using pinned submodules and the correct test flag

[Copilot]

The current GitHub Actions CMake workflow has room for improvement around reproducibility and correctness. It was overriding pinned submodule revisions at CI time and passing a CMake option the project does not use.

• Use repository-pinned submodules

  • Switch checkout to submodules: recursive so nested dependencies are fetched directly by actions/checkout.
  • Remove the manual submodule update step that pulled cppjieba from remote master, which made CI depend on upstream head instead of the revision pinned in this repo.

• Use the project’s actual CMake test toggle

  • Replace -DBUILD_TESTING=ON with -Dsimhash_BUILD_TESTS=ON to match the option defined in the top-level CMakeLists.txt.

• Net effect

  • CI now builds against the exact submodule revisions tracked by the repository.
  • Test targets are enabled through the option the project actually consumes.

- uses: actions/checkout@v3
  with:
    submodules: recursive
    fetch-depth: 0

- name: Configure CMake
  run: cmake -B ${{github.workspace}}/build -Dsimhash_BUILD_TESTS=ON -DCMAKE_CXX_STANDARD=${{matrix.cpp_version}} -DCMAKE_BUILD_TYPE=${{matrix.build_type}}

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.