Skip to content

Update .gitmodules #11

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.

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

taraspos
Copy link
Contributor

No description provided.

Copy link

github-actions bot commented Jun 2, 2025

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
taras/attempo-to-make-shallow-clone-work 5cf24f5 8 ❌FAILED taras-attempo-to-make-shallow-clone-work 2025-06-02 13:29:15

@taraspos taraspos force-pushed the taras/attempo-to-make-shallow-clone-work branch from 261050c to 5cf24f5 Compare June 2, 2025 13:14
@ptgott
Copy link
Contributor

ptgott commented Jun 2, 2025

Is there a way to ensure that the submodule clones remain deep on local docs-website clones? I've had issues in the past with setting up a docs-website clone and not being able to work with the commit history in the content submodules

@taraspos
Copy link
Contributor Author

taraspos commented Jun 2, 2025

This doesn't seem to do anything, Amplify still takes almost 5 minutes to get submodules cloned:

2025-06-02T13:21:33.892Z [INFO]: # Updating Git submodules...
2025-06-02T13:25:05.769Z [INFO]: # Retrieving environment cache...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants