Files
Cristian Magherusan-StanciuandClaude Sonnet 5.5 4c9b0c9618 ci: use canonical module origins for fork checkouts
Fork checkout resolves relative module URLs against forks that do not
contain the module repositories, so all three legacy jobs fail before
compilation. Check out the superproject first and temporarily select the
canonical origin for native recursive Git initialization. Restore the
exact configured origin on success and failure without logging it.

Submodules are fetched shallow (--depth=1) with the same flags as
actions/checkout@v4, and git output is left visible in the job log.
submodules: false also skips the checkout action's global auth setup, so
submodule fetches are anonymous (fine for the public modules).

Behavior follows native Git relative-submodule resolution. Tracked
metadata, pinned commits and the existing job build steps are unchanged.

Verified with python3 scripts/ci/test_checkout_submodules.py (ten tests
against real Git repositories). Hosted checkout authentication and
runtime compilation are not verified.

Related: VibeDarling/darling#1181

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
2026-10-16 13:21:46 +02:00
..