A full (or full master branch) clone was well over 4 hours.
A shallow (--depth 1) clone would take like 5 seconds.
A pull origin master on a local copy that was less than 2 days old was well over an hour.
I was using GitHub Actions to get the latest 'total commit count'. I was actually using https://github.com/actions/cache to cache a full repo clone, pull origin master then update that cached copy after to not have to do a full repo clone each time. At that point run a rev-list command to get the count.
Doing that process would take a few minutes.
I also recently started having GitHub Actions make more branches to be auto merged into master. They allow actions to be run every 10 minutes, so I was having it make commits for 10 minutes then it would push temp branches that would be PR'd and merged via the gh cli by my locally running instance.
Just that 10 minutes of commits would be over 4500 commits per branch. Doing the push from that point would take about 2 minutes.
Part of me wants to try to look into the git cli to try to see why some of the hangs happen. I don't think any sort of hang with no output (at least with -v) should happen normally.
In the defense neither did or will