`exp`: CI runs require unshallow clone (fetch-depth: >1)
See original GitHub issueSummary: dvc exp
commands will not run in CML or other Github actions (and probably the same on other Git servers?) because they will only fetch the head commit by default, which is insufficient for internal git merge
s. The solution is in https://github.com/iterative/dvc/issues/7547#issuecomment-1088702706.
Not sure where to document this or even whether it belongs in DVC, CML, or both. @casperdcl Maybe you have thoughts?
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
`fetch-depth: 1` and not cloning tags are dangerous defaults ...
I've noticed that lerna runs & versions incorrectly in my github actions workflow, but once running lerna version locally, everything works fine ...
Read more >Shallow fetch for repository - Stack Overflow
I have an Azure Pipeline (yaml) which uses templates and I'm trying to figure out how to setup the fetch depth of the...
Read more >How and when to perform a git clone depth 1 example
In this git clone depth 1 example, we'll walk you through the process of pulling only one commit and one branch back from...
Read more >Get up to speed with partial clone and shallow clone
git clone --depth=1 <url> creates a shallow clone. These clones truncate the commit history to reduce the clone size.
Read more >GIT_DEPTH=0 does not work as expected, it does not ... - GitLab
The only work-around I found was to add - git fetch --unshallow ... Project Setting "Git shallow clone" and "GIT_DEPTH" no longer working....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
definitely docs in both because
Makes sense to mention in:
What about creating a new section in https://dvc.org/doc/user-guide/troubleshooting , catching the specific exception on DVC side, and make it point to that URL