Maybe we can add an auto delete for branches older than one year
deleted mine. But I do have 1 old one which I need to keep @philbucher
I checked, there are a lot of branches that don't have a single commit to them.
I would say we can safely delete those, what do others think?
@philbucher I have old branches that must not be deleted, even with old commits, please check if it is written or not "DO NOT DELETE" if you proceed.
PS. Sorry for closing the issue, I re-opened it.
Please, ask before delete other people's branches.
I won't delete anything, just throwing ideas
as @loumalouomega pointed out we have > 500 branches, and many many are stale. At some point I fear that this will become a performance issue with Git.
Hence I suggest to find a better solution
BTW if there are some branches that must not be deleted, then we could think of protecting those (like the master or the release branches)
@KratosMultiphysics/technical-committee also highly recommends revising the old branches and eventually think about adding an automatic mechanism to alert the developers for stale branches and delete them if there are no merge from master to it in one month after the notification.
@KratosMultiphysics/technical-committee also highly recommends revising the old branches and eventually think about adding an automatic mechanism to alert the developers for stale branches and delete them if there are no merge from master to it in one month after the notification.
I added an action (recommended by GitHub) for that: https://github.com/KratosMultiphysics/Kratos/pull/6156
I am not an expert in actions, can any expert check how can this work?
@KratosMultiphysics/technical-committee will eventually implement a mechanism with which ppl will be informed if they have stale branches. Preliminary investigations show that this can work
Most helpful comment
I checked, there are a lot of branches that don't have a single commit to them.
I would say we can safely delete those, what do others think?