On 10/7/19 12:13, José Iván López González wrote:
Hi guys,
Hi!
I see we have several temporary branches in many YaST repos, [...]
[...]
Regarding this topic, past Friday I was doing the SLE-12-SP5 branching and I took the opportunity to remove (through the Github interface) all branches which were related to a merged or closed pull request. Namely, yast-autoinstallation module-config-builder-nil master-bsc-1138144 SLE-12-SP4-bsc-1134501 yast-core Code-11-SP3-bnc-1103076 clang yast-country master-bsc-1120957-2 review_171117_build_fix yast-devtools fix-929899 yast-dhcp-server SLE-15-GA-bsc-1108942 master-bsc-1108942-2 SLE-12-SP2-bnc-932331 yast-dns-server review_180604_merged_with_sles15 SLE-15-GA-bnc1093029 yast-auth-server update-desktop-files yast-bootloader update-desktop-files yast-alternatives update-desktop-files yast-online-update update-desktop-files yast-migration update-desktop-files yast-firewall fixes SLE-12-SP3-1119831 merge_SLE-12-SP4 move_things SLE-15-GA_wrong_bug_id master_bnc_1089855 review_180223_textdomain_added review_180219_fixed_rnc_file review_180104_ay_read yast-ftp-server master_bnc_1047232 SLE-12-SP3_bnc_1047232 yast-hardware-detection fix-bsc-903069-master yast-installation-control backport_mitigations added_test master-registration-popup feature/fate-325482-include-self-update-version-in-control-file yast-installation aschnell-patch-1 sw_03 SLE-12-SP5-bsc-1122303 feature/fate-325482-include-self-update-version-in-control-file feature/fate-325746 sp4_merge sle15_merge yast-instserver sw_01 yast-isns hardening yast-journal build_fix dialog query_refactor rubocop split_dialog_further yast-kdump aschnell-patch-1 yast-mail varkoly-patch-1 drop_perl_from_yast2 yast-migration aschnell-patch-1 yast-multipath SLE-15-GA-key fix_killing yast-ntp-client data_to_include yast-packager mock_arch offline_medium product-license-translation-m master-bsc-1132622-3 feature/port-changes-from-4.1.35 SLE-15-SP1-bsc-1077399 unify_labels SLE-15-GA-bsc-1105758 sle12sp3_bsc_1078323 yast-perl-bindings deprecate-yapi yast-python-bindings obs_docker yast-rdp GPL-2.0-only SLE-15-GA-key yast-registration message_update merge_sp3_fix SLE-15-GA_1043125 SLE-15-GA_bnc_1090911 update_changes review_180702_merge_sles15 selected_product try-base-regcode-first yast-s390 sw_02 sw_01 aschnell-patch-1 yast-samba-server aschnell-patch-1 SLE-15-GA-key yast-schema SLE-15-SP1-1128707-2 SLE-15-SP1-1128707 master-1108199-3 merge-sle-15-ga review_151008_is_opensuse review_151006_spec_is_opensuse yast-services-manager feature/test-and-refacor-import-export-methods respect_sockets SLE-15-GA-1113732 ay_x11_test yast-snapper merge_SLE-12-SP1 yast-sound bnc_845928 yast-testsuite dejagnu-16 ignore_includes yast-tftp-server feature/fix-service-start yast-theme alt-branding-sp1 master-link hardcoded-color yast-transfer fix_killing_12 yast-tune SLE-15-GA-key yast-update SLE-15-SP1-bsc-1136012 mount-run-during-upgrade yast-users master-bnc-1118617 SLE-15-GA-bnc-1118617 yast-yast2 new_rubocop merge_SLE-12-SP4 SLE-15-GA-1113732 merge_SLE-12-SP3 SLE-15-GA-registration-popup systemd_table better_socket_support expanded_ids yast-ycp-ui-bindings open-close-ui
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].
But, of course, to extend your HW project to do an automatic clean up is welcome :) as well as to reach a workflow agreement about how to manage the temporary branches: we could stop using the upstream repos or simply try to always delete no longer necessary branches.
CU, Iván
Regards. -- David Díaz González YaST Team at SUSE Linux GmbH