We could just delete all branches that are ancestors of master (meaning
they have no commits that are not in master) and haven't been updated in X
days. We could also extend that to branches that may not have been merged
yet, but also haven't been touched in over 2 years. (Noting that deleting
a branch on gitlab doesn't delete those branches on developers' local
machines.)
Thoughts?
Thanks,
Jason
On Tue, Dec 22, 2020 at 9:56 AM David A Case <david.case.rutgers.edu> wrote:
> Hi everyone:
>
> We have a very large number of branches for the amber repository at
> gitlab.ambermd.org. So many, that the GUI can't list them all.
>
> You can see the branches by typing "git remote prune origin", followed
> by "git branch -a". If you see branches that you made but which are no
> longer needed, please remove them by typing "git push origin --delete
> <branchname>".
>
> ...thanks...dac
>
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
>
--
Jason M. Swails
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Tue Dec 22 2020 - 08:30:02 PST
