Replies: 2 comments 1 reply
-
|
My code repo is quite big, like 80G size, so can i set the fetchDepth = 1 or fetchDepth=200 ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @DxWang36, The fetch depth constraint comes from Git. To execute the command for determining the set of changes, Git requires certain historical Git commit data. It's hard to give a definitive answer as to how much history is required due to the way Git works, and due to differences in the way commits could be made. If If that doesn't work, the only solution would be to flatten some of the Git commit history, but this probably isn't advisable as it would change the commit info. Hope this helps. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
when I run the PR-Metrics Task, it report a error
##[error]Could not access sufficient Git history. Set 'fetchDepth: 0' as a parameter to the 'checkout' task (YAML) or disable 'Shallow fetch' under the build process phase settings (classic).
So it means that I must use fetchDepth:0 ? my code repo is quite big, can I just pull a little commit?
Beta Was this translation helpful? Give feedback.
All reactions