Git, GitHub, and gaming
summary
Explains why git works for text but struggles for games: binary assets, huge file counts and sizes, and messy diffs. Gives concrete examples: a tiny Unity microgame with 17,170 files in 751 folders, a 5‑second trailer at 57 MB, and the practical limit of Git LFS 5 GB. Shows GitHub collaboration features actually used: issue forms, Projects (boards/timeline), Discussions, and web previews for some media and 3D diffs. Suggests open source engines and game jams (GitHub Game Off) as low‑friction entry points.
AI-written summary · about
chapters (11)
- 0:00Introduction to Git
- 3:08Understanding Git
- 6:11Collaboration Pillars
- 10:21GitHub Collaboration Tools
- 17:15Social Coding Platform
- 18:53Challenges in Game Development
- 25:00Managing Large Files
- 30:34File Management Issues
- 36:46Game Companies and Git
- 40:55Getting Involved in Gaming
- 47:33Resources and Q&A
related talks
53mThe Power of Modern Version Control
27mTaking code to next level with Open Source (Git & Github)
17mProject Immortality: Using GitHub To Make Your Work Live Forever
17mProject Immortality: Using GitHub To Make Your Work Live Forever
58mAdopting open source in your organization
01h 06mHow GitHub delivers GitHub using GitHub
01h 02mOpen Sourcing Your Tech Stack - How I Saved $5000 and Still Made a Game
43mTop Ten Worst Repositories to host on GitHub
