Vivien Kraus wrote: > However, there are situations in which you only have access to a > shallow clone of the git repository (for instance, Gitlab CI). I am not > sure how this solution would work in that case.
The shallow clone is an optimization, that was based on the assumption that the CI does not need the git history. For CI runs that produce tarballs in this way, and that need to look into the git history, a full clone will be needed. Bruno
