-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Allow to set git clone depth #9708
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
Comments
Hi @DifferentialOrange! You can use https://docs.readthedocs.io/en/latest/build-customization.html#unshallow-clone to unshallow your repository. Let me know if that doesn't work for you for any reason. |
Use unshallow clone [1] to negate the default readthedocs clone with depth 50. 1. readthedocs/readthedocs.org#9708 (comment) Closes #255
Use unshallow clone [1] to negate the default readthedocs clone with depth 50. 1. readthedocs/readthedocs.org#9708 (comment) Closes #255
Use unshallow clone [1] to negate the default readthedocs clone with depth 50. 1. readthedocs/readthedocs.org#9708 (comment) Closes #255
That helped. Thanks a lot! |
Use unshallow clone [1] to negate the default readthedocs clone with depth 50. 1. readthedocs/readthedocs.org#9708 (comment) Closes #255
Details
We use setuptools_scm to compute our package version automatically based on git metadata. Documentation displays the package version.
Expected Result
setuptools_scm successfully computes package version in every case.
Actual Result
setuptools_scm fails to compute expected package version if there are more than 50 commits since last tag.
Since git clone depth is 50 in build pipeline, tag info is not fetched and it displays
0.1.dev50+g26c6db1
version instead of0.9.1.dev73+g26c6db1
. It would be nice to be able to tune git clone settings to fix such behavior.The text was updated successfully, but these errors were encountered: