Cloning large packages using git (1+ GB, 100k+ files) is slow and the 300s timeout is not enough.

Shallow clone #3449 can help, #5384 still does not solves this issue completely (composer timeouts when cloning to the cache, and when cloned manually to the cache first, the default 300s timeout is not enought even to clone from this cache). However I understand shallow clone might not be always the solution.

This issue is a feature request to NOT timeout if the git reports progress.

Example:

remote: Enumerating objects: 1910, done.
remote: Counting objects: 100% (1910/1910), done.
remote: Compressing objects: 100% (122/122), done.
Receiving objects:  1% (80227/7686857), 18.77 MiB | 4.66 MiB/s

and when the Receiving objects count is increased, reset the process timeout. The git progress should be reported also to the user. Currently, there is not progress visible at all.