Skip to content

fix(git): submodule update command uses an unsupported option #6454

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

Jump to bottom
Merged
merged 8 commits into from
Aug 27, 2025
Merged

fix(git): submodule update command uses an unsupported option #6454

merged 8 commits into from
Aug 27, 2025

Conversation

broesch
Copy link
Contributor

@broesch broesch commented Aug 27, 2025 •
edited by peaklabs-dev
Loading

Changes

  • use --depth=1 instead of --shallow-submodules as git submodule update does not support --shallow-submodules

Issues

@peaklabs-dev peaklabs-dev changed the base branch from v4.x to next August 27, 2025 14:48
@peaklabs-dev peaklabs-dev changed the title Fix issue with submodule deployment: Use correct git parameter fix(git): submodule update command uses an unsupported option Aug 27, 2025
@peaklabs-dev peaklabs-dev merged commit c2ff9ea into coollabsio:next Aug 27, 2025
1 check passed
@peaklabs-dev
Copy link
Member

Thanks for the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Bug]: Submodule uses wrong parameter for creating shallow clone
3 participants
@broesch @peaklabs-dev @andrasbacsai