> As it turns out, we only run repacks on a repository network level, which means that repacks need to consider objects from all forks of a given repository.

> Repacking entire repository networks will always lead to less optimal pack sizes compared to repacking just objects from a single fork. For GitHub, disk space is not the only thing we optimize for, but also performance across forks and client performance.

So the lesson here is you can DoS existing open source projects somehow by forking them and increasing the forked repo size >2GB?