So you've got a repo with 87,365 branches and GitHub is down for the count. Look, we've all been there – well, maybe not with that many branches, but close enough. That's what happens when your team treats "delete merged branches" like it's optional and everyone's too scared to clean up because "what if we need that feature-branch-final-FINAL-v2-actually-final from 2019?" The pun is chef's kiss though. "Rooting" for Microsoft because you've got so many branches your repo looks like a forest. Get it? Branches? Roots? I'll see myself out. Real talk: if your repo has more branches than a Denny's has menu items, it's time for some spring cleaning. Your CI/CD pipeline is probably crying in a corner somewhere.