Disable shallow clone for Jitify dependency in CMake configuration

[a-hirota]

Description

Change GIT_SHALLOW from TRUE to FALSE to ensure complete repository history is available during build. This improves build stability by providing access to the complete Git history when needed.

This change affects the Jitify dependency configuration in cpp/cmake/thirdparty/get_jitify.cmake and helps prevent potential build issues that may occur when the build system requires access to the full Git repository history.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[Copilot]

Pull Request Overview

This PR disables shallow clone for the Jitify dependency in CMake configuration by changing GIT_SHALLOW from TRUE to FALSE. This ensures the complete Git repository history is available during the build process, which can improve build stability when the build system requires access to the full repository history.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[davidwendt]

/ok to test

[copy-pr-bot]

/ok to test

@davidwendt, there was an error processing your request: E1

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/

[davidwendt]

/ok to test 085b71b

[bdice]

Thank you @a-hirota! I would like to merge #19783 instead. It also contains a separate fix that is needed.

[TomAugspurger]

@a-hirota #19786 ended up including this change to get CI passing. Would you be able to pull branch-25.10 and confirm that things work for you?

[a-hirota]

@TomAugspurger Thank you for incorporating this change in #19786!

I've tested branch-25.10 and can confirm:

• The build completes successfully with the Jitify update
• No build errors encountered

Everything looks good to me. Should I close this PR since the fix is now included in #19786?

[TomAugspurger]

Yep, I think we're all set now. Thanks for making the PR, and sorry we didn't get it in before those other issues came up.