Discussion: Lots of Private Branches

[michael-hawker]

Discussion: Private Branches

We had an issue on the Windows Community Toolkit about the number of non-active/private branches we had on the main repo: CommunityToolkit/WindowsCommunityToolkit#3321

Looks like WinUI is getting more branches too, which makes it a bit harder to realize there's release branches for each release.

Contributors should instead fork the repo and create branches in their forks and then create pull requests from there.

I've been considering turning off write access for branches on the main repo to ensure contributors use forks as well...

Just wanted to carry this suggestion forward.

[StephenLPeters]

@ranjeshj and @jevansaks FYI

[jevansaks]

The PR policy to delete branches after merge helped a lot. But there's still quite a lot of stale non-working branches. Perhaps people who don't clean up their stale branches get their repo write permissions revoked? 😲

[kmgallahan]

@anawishnoff

ಠ_ಠ

[anawishnoff]

@kmgallahan just cleaned some of mine up :)