On Thu, 10 Nov 2022 at 20:38, Scott Kostyshak <skost...@lyx.org> wrote:
> Should we delete branches from the features repo that have been merged > to master? I don't know our policy on this, but it's hard to figure out > which branches on the features repo are still relevant (i.e., not yet > merged). In the worst case scenario, e.g., where we need to revert the > merged branch on master, it is easy to push it again to features. > +1: it's really a mess, even though it only has like 25 branches. > Similar question for features/biblatex. I haven't looked through the > other branches yet. > > I don't know git well, but from what I understand we need to do > something like the following: > > # remove the "-n" if this does indeed look correct > git push -n features --delete features/indexmacros > It seems it's possible to "hide" a branch while still keeping it around: https://stackoverflow.com/questions/25169440/remove-hide-git-branches-without-deleting-commit-histories
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
