Skip to content

fix(ci): don't recurse submodules when bumping the engine pointer #156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Seungpyo1007 merged 1 commit into from
Aug 10, 2026
Merged

fix(ci): don't recurse submodules when bumping the engine pointer #156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions .github/workflows/bump-engine.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,8 +38,13 @@ jobs:
# committed to.
git fetch origin develop
git checkout -B develop origin/develop
git submodule update --init --recursive TechEngine
git submodule update --remote --recursive TechEngine
# NOT --recursive. TechEngine carries TechAPI back as a submodule, so
# recursing follows that cycle — TechEngine/TechAPI/TechEngine/… — and
# each level re-fetches the million-file data tree until the runner
# reports "No space left on device". The gitlink being bumped is at
# this repo's top level; there is nothing below it to update.
git submodule update --init TechEngine
git submodule update --remote TechEngine
if git diff --quiet -- TechEngine; then
echo "changed=false" >> "$GITHUB_OUTPUT"
echo "Submodule already up to date — nothing to do."
Expand Down
Loading