Tidy up non-active branches

[nickrandolph]

There are currently 118 branches with no coherent branching strategy.

To make it easier for contributors, please:

• purge non-active branches
• adopt a model where contributors (all) work in private forks and push all changes via a PR to the main WCT repo
• if some contributors continue to work on main repo, please propose a branching strategy that makes sense

Hello nickrandolph, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

@nickrandolph Thanks for highlighting the issue. We will discuss these options and explore ways we can improvise the process 🙌

[michael-hawker]

As a note to my future self, we should also document how we work with branches and what our current active branches are.

[nickrandolph]

cc @nmetulev @hermitdave @cbarkerms @clairernovotny @VisualByteStudios @deltakosh @jwilcox1701 @normesta @rjmurillo @TGoodhew @JustinXinLiu
Can you please review any branches that you have and delete them if they're no longer relevant. If relevant, can you rebase them so we know they're still active
I know this is a road map item but the admin responsibility shouldn't just fall on @michael-hawker

[michael-hawker]

Thanks @nickrandolph, @Kyaa-dost @RosarioPulella and I went quickly over them this morning as well, there are a lot I know from some folks which are just stale and we can get rid of from past projects too. 🙂

@Kyaa-dost I think you have the right permissions to get rid of ones from tgoodhew, rjmurillo, and jwilcox1701 that we know are all from past projects?

[TGoodhew]

If you need me to I'm happy to delete those old dead decaying and, frankly, somewhat smelly branches with tgoodhew on them.