ARUN PRAVEEN P’s Post

GitHub Repository Setup: From 600MB of Chaos to 37MB of Clean Code Just spent the morning wrestling with Git, merge conflicts, and 128MB executable files that kept getting rejected by GitHub. Here's what I learned (so you don't have to spend 45 minutes debugging the same error). THE CHALLENGE: Created a new GitHub repo for our Weider3 project Tried to merge two branches with parallel development Hit the wall: Build artifacts exceeding GitHub's 100MB limit (multiple times) 30+ recurring errors, same issue THE PAINFUL REALITY: When you commit compiled .exe and .pkg files to Git, they stay in your history FOREVER. Updating .gitignore doesn't fix already-committed files. This cost us significant time. THE SOLUTION: text git filter-branch --tree-filter 'rm -rf build exe' -f HEAD Result: Repository size 600MB → 37MB. Clean push successful. KEY LESSONS (Share These With Your Team): 1. Create .gitignore BEFORE your first commit 2. Never commit build artifacts or binaries 3. Generate builds in your CI/CD pipeline, not locally 4. Merge frequently (every 2-3 days, not weekly) 5. Communicate file changes with your team THE MERGE CONFLICT PART: Had conflicts in slip_formats.py, report_formats.py, and camera_config.json. Both branches modified them independently. Used git merge -X theirs to resolve automatically, then manually reviewed. OUTCOME: ✓ Clean GitHub repository ✓ Successful team collaboration framework ✓ Documentation for future developers ✓ No more "file size exceeded" errors IF YOU'RE JUST STARTING LIKE ME: Stop treating Git like a necessary evil. Treat it like a safety net. Your future self will thank you. What's your biggest Git pain point? Drop it in the comments 👇 #Git #GitHub #SoftwareDevelopment #DevOps #Python #CodingTips #IndustrialAutomation

To view or add a comment, sign in

Explore content categories