-
Notifications
You must be signed in to change notification settings - Fork 361
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
chore: Recommend git clone --recursive for submodules #4036
Conversation
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for updating the docs. what does --recursive do? we might want this one instead. --recursive
doesn't show up in git clone --help
--recurse-submodules[=<pathspec>]
After the clone is created, initialize and clone
submodules within based on the provided pathspec. If no
pathspec is provided, all submodules are initialized
and cloned. This option can be given multiple times for
pathspecs consisting of multiple entries. The resulting
clone has submodule.active set to the provided
pathspec, or "." (meaning all submodules) if no
pathspec is provided.
Submodules are initialized and cloned using their
default settings. This is equivalent to running git
submodule update --init --recursive <pathspec>
immediately after the clone is finished. This option is
ignored if the cloned repository does not have a
worktree/checkout (i.e. if any of --no-checkout/-n,
--bare, or --mirror is given)
I'm considering whether we want to add a |
oh I had used I'll update this PR and then if you think it should combine in the |
thanks.
i'll try this in saas and see how that works out first. |
Description
Update our docs where we
git clone
to include the new submodules withgit clone --recursive
Checklist
docs/release-notes/
.