-
Notifications
You must be signed in to change notification settings - Fork 898
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
Docsy 0.4.0 migration instructions and doc updates #1074
Docsy 0.4.0 migration instructions and doc updates #1074
Conversation
|
||
git submodule update --init --recursive | ||
{{% /alert %}} | ||
1. Ensure you have an up to date local copy of your site files cloned from your repo. |
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.
I simplified this because, IMHO, we shouldn't be telling folks how to clone their own repos -- in particular because we don't know the flags that they require.
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.
Works for me, the only reason we used to have to remind people to recurse into the submodules was because of FontAwesome and Bootstrap, we had a lot of users who cloned sites that didn't work because they were missing those submodules.
This looks great! Do you want to hold off on merging or can I merge now? |
Thanks for the docs tweak and LGTM. This is ready to merge now. |
* Docsy 0.4.0 migration instructions and doc updates * Also drop --recurse-submodules * tiny fix Co-authored-by: LisaFC <lcarey@google.com>
Preview: