-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Updated the document with an example of Git depth. for issue#34676 #34692
Conversation
Co-authored-by: runephilosof-karnovgroup <101270124+runephilosof-karnovgroup@users.noreply.github.com>
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.
Remember to also delete lines 283-285 which are now repeated in the new text.
Please approve this PR |
@vinod827 I've reached out to the docs team for a review. Thanks for your patience! |
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 fixing this. I added a few tweaks to fix the grammar.
Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
This PR fixes the issue# #34676 where the documentation was unclear to the developers concerning the
git clone ---depth
during shallow cloning of a git repository. It describes the git depth in detail with an example.Fixes #
#34676