PyTorch repo has 14,971 branches

Is this really sane project management?

When a branch is merged into master, why not delete the branch?

And only persist branches corresponding to public releases…

I’m now counting 14,974

Screenshot 2023-02-17 at 06.56.18.png

3 branches in 3 mins then … :grimacing:

^ @TeamPyTorch I have this guy’s number if you’re looking for a ProjectManager/devops.

A lot of non-release branches seem to be a few years behind without any commit

I see a lot of gh/username/head, gh/username/orig, gh/username/base branches and am wondering if these dead branches are left by ghstack.
CC @ezyang in case these could be cleaned up.