I'm facing issues with a repository that has a very long history, even though it is not heavy by itself.
As the git-clone task is implemented, every time there is a clone action, the cluster clones the entire repository, which is not efficien; especially when there are large repos (due to long histories).
I propose to implement git shallow clone for the git clone task, instead of the regular clone
proposal:
git clone --depth=1 $REPO_URL $SUBDIR
Original:
git clone $REPO_URL $SUBDIR