-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Tidy up non-active branches #3321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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 🙌 |
@nickrandolph Thanks for highlighting the issue. We will discuss these options and explore ways we can improvise the process 🙌 |
As a note to my future self, we should also document how we work with branches and what our current active branches are. |
cc @nmetulev @hermitdave @cbarkerms @clairernovotny @VisualByteStudios @deltakosh @jwilcox1701 @normesta @rjmurillo @TGoodhew @JustinXinLiu |
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? |
If you need me to I'm happy to delete those old dead decaying and, frankly, somewhat smelly branches with tgoodhew on them. |
Thanks, @michael-hawker will clean it up. @TGoodhew if you have any stale branches that are closed or non-active please feel free to delete them, thanks 😄 |
Just tried - Looks like I don't have permissions - Sorry |
@Kyaa-dost / @azchohfi are you able to assist @TGoodhew with tidying up branches? |
@nickrandolph Yes, all clear! |
Things are looking a lot better now, appreciate everyone's help on this project! Wondering if we want to close down write access to the repo to force people to have to submit from forks? Thoughts? |
I think that's a great idea as there is still a possibility of mishaps. This will be one way to stop and we can always provide Write access to individuals based on requests or severity of the work. |
I propose that we use git flow for branching strategy and Fork-PR model for contributing.
Also, with explosion of the UWP Controls projects, the naming of folders is becoming long with |
@Nirmal4G yeah. I'm thinking of locking down write access on the main repo, as we can just fork and do PRs for the things we need, and only admins do the release work anyway currently. There's a couple of branches we can't delete (one of them is odd and like a zombie (https://github.com/windows-toolkit/WindowsCommunityToolkit/tree/DwayneUWPCTKSandbox - can't get rid of it). Going to close this issue for now. @Kyaa-dost we should probably open up an issue around this topic and better guidance in our Wiki repo from the governance side. At least from an action of the original intent of the issue, I think we're good. Thanks for the help @nickrandolph! |
The zombie branch with my name in it looks like it might have been an experimental branch I created back when we were first learning how to add pages to the Toolkit.
I am pretty confident that there is nothing important in there if you are able to kill it from your end.
|
There are currently 118 branches with no coherent branching strategy.
To make it easier for contributors, please:
The text was updated successfully, but these errors were encountered: