How to fix fatal: the request was too large; try breaking it up in Git

# Check how many commits are ahead of remote
git log origin/main..HEAD --oneline | wc -l

# Push commits in batches using specific commit SHAs
# First, find a commit roughly halfway through your unpushed commits
git log origin/main..HEAD --oneline

# Push up to a specific commit
git push origin <commit-sha>:main

# Repeat until all commits are pushed
git push origin main

# Push first 25 commits
git push origin HEAD~75:main

# Push next 25
git push origin HEAD~50:main

# Push next 25
git push origin HEAD~25:main

# Push remaining commits
git push origin main

# Increase buffer to 500 MB
git config --global http.postBuffer 524288000

# For very large repositories, try 1 GB
git config --global http.postBuffer 1048576000

# Check your Git version
git --version

# If older than 2.9, consider upgrading first

# Check current remote URL
git remote -v

# Change from HTTPS to SSH (GitHub example)
git remote set-url origin [email protected]:username/repository.git

# For GitLab
git remote set-url origin [email protected]:username/repository.git

# For Bitbucket
git remote set-url origin [email protected]:username/repository.git

# Verify the change
git remote -v

# Now try pushing
git push origin main

# Generate SSH key if needed
ssh-keygen -t ed25519 -C "[email protected]"

# Add to SSH agent
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519

# Copy public key to add to your Git hosting service
cat ~/.ssh/id_ed25519.pub

# Install Git LFS
git lfs install

# Track large file types
git lfs track "*.zip"
git lfs track "*.tar.gz"
git lfs track "*.bin"
git lfs track "*.dll"
git lfs track "*.so"

# Add the .gitattributes file
git add .gitattributes
git commit -m "Configure Git LFS tracking"

# Migrate existing large files to LFS (if already committed)
git lfs migrate import --include="*.zip,*.tar.gz" --everything

# Force push after migration (careful!)
git push --force-with-lease origin main

# Clone with limited history
git clone --depth 1 https://github.com/username/repository.git repo-shallow
cd repo-shallow

# Add your new remote (if different)
git remote add target https://github.com/username/new-repository.git

# Push the shallow clone
git push target main

# If you need full history, fetch it incrementally
git fetch --deepen=100
git push target main
# Repeat until full history is transferred

# In nginx.conf or site configuration
server {
    # Allow unlimited request size
    client_max_body_size 0;

    # Or set a specific large limit
    # client_max_body_size 1024m;

    # Disable request buffering for streaming
    proxy_request_buffering off;

    # Increase timeouts for large transfers
    proxy_read_timeout 300;
    proxy_connect_timeout 300;
    proxy_send_timeout 300;
}

# In httpd.conf or .htaccess
LimitRequestBody 0
TimeOut 300
ProxyTimeout 300

# Find large files in history
git rev-list --objects --all | \
  git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' | \
  sed -n 's/^blob //p' | \
  sort -rnk2 | \
  head -20

# Remove large files from history using git-filter-repo (recommended)
# Install: pip install git-filter-repo
git filter-repo --invert-paths --path path/to/large/file

# Or remove by size (removes files over 100MB from history)
git filter-repo --strip-blobs-bigger-than 100M

# Run garbage collection
git gc --aggressive --prune=now

# Force push the cleaned repository
git push --force-with-lease origin main

# Check if proxy is configured
git config --global --get http.proxy
git config --global --get https.proxy

# Temporarily bypass proxy (if allowed)
git config --global --unset http.proxy
git config --global --unset https.proxy

# Or set NO_PROXY for Git hosts
export no_proxy="github.com,gitlab.com,bitbucket.org"

# Try push again
git push origin main

# Re-enable proxy if needed
git config --global http.proxy http://proxy.company.com:8080