José Iván López González
Hi guys,
Hi Iván,
I see we have several temporary branches in many YaST repos, for example in yast-storage-ng:
[..]
Having all these temporary branches is not a big problem, but sometimes it is quite annoying when you run a "git fetch". What do you think about doing some cleanup in all YaST repos?
I could extend my HW project [1] (still a WIP) to do it. It should be quite easy to add a new script to clean the repos. The good thing is that it is not necessary to locally clone the repos. With [1] we have the base to do it directly to GitHub thanks to Octokit [2].
We should be extremely careful to not remove a branch which is still being used. Think, for instance, about features branches like `network-ng` in yast2-network. Not to mention the branches of those people who (like me) do not use a fork to create a PR, but a branch in the original repo. In other cases, we could have some PoC in a separate branch which has not been updated in a while. We can discuss whether we should use branches in upstream repos to create our own PRs or not (I do, but I am open to discussion). Thinking aloud, I guess we could try to get a list of unexpected branches and a responsible for each of them to check whether they are still needed or not. BTW, nice Hack Week project :) Regards, Imo -- Imobach González Sosa YaST Team at SUSE LINUX GmbH https://imobachgs.github.io/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org