What's the total disk-size usage of all those repos checked out locally? Sounds like you should just have rely on git (or mercurial?) itself for the whole thing

What's the total disk-size usage of all those repos checked out locally? Sounds like you should just have rely on git (or mercurial?) itself for the whole thing. For example on an EC2 VM which persists the repos on an EBS volume, spins up, calls the API only to get a list of created/moved repos, clones and fetches, then from there you operate on everything locally. I've done similar analysis for orgs with same order of magnitude of repos on both GH and BB. No need to re-implement caches, diffing, or other optimizations that the VCS already handes for you. Sorry to say it but sounds the requirements were completely sane and realistic.