(The issue described here probably doesn’t affect most of the members but I think it’s still a good idea to give a heads-up for people who have a similar workflow)
If you happened to push the entire llvm-project to another new (personal) GitHub repo recently, you might encounter the following error message before the whole process bails out:
... remote: fatal: pack exceeds maximum allowed size (2.00 GiB) error: remote unpack failed: index-pack abnormal exit To github.com:<your GitHub repo> ! [remote rejected] main -> main (failed) error: failed to push some refs to 'firstname.lastname@example.org:<your GitHub repo>'
The crux here is that we tried to push the entire repo, which has exceeded GitHub’s upload limit (2GB) at once. This is not a problem for majority of the developers who already had a copy of llvm-project in their separated GitHub repos (or simply lack such kind of copy) since incremental commit pushes are unlikely to exceed the upload limit.
If you don’t really care about the full git history and/or some other branches, the easiest fix will be using Git shallow clone to clone the upstream llvm-project tree before pushing it to another GitHub repo.
Otherwise, you might want to push the repo in parts:
git checkout <a previous commit when the project size was still under 2GB> # Push first half of the commits git push <remote name> HEAD:refs/heads/<remote branch name> # Push rest of the commits git checkout <local branch name> git push <remote name> HEAD:<remote branch name>
For the ‘commit when the project size was still under 2GB’ , I randomly picked one from 2021. As I remember the issue only happened recently.