El 2025-06-21 11:47, Andreas Enge escribió:
Hello,over the past few days I see branches pop up on the main Codeberg repo that I think are pushed inadvertantly; this concerns branches by jgart and vagrantc (sorry, this is not meant as a name and shame, but so that you/we can investigate what happens). For instance, python-team-pypy-fix-load-path lisp-team-asdf-build-system/clasp lisp-team-asdf-build-system-clasp librecast-0.11.2 I have seen some such branches persist even after their HEAD was pushed to master. So to me it looks as if somehow your workflow pushes what should remain local branches, or maybe pull request branches, to the main repo; and that there are at least two committers shows that this happens in a "natural" workflow. Do you have an idea what is happening, and how it can be prevented in the future? Thanks for your help, Andreas
My guess is because the merge happened locally (on their computers, because of signing requirement), they need to push to delete the upstream branch too, e.g.
git push origin :librecast-0.11.2
Alternatively folks can maintain own forks, and merge from that,
therefore not leaving such unused artifacts. Another problem with
leaving these artifacts at upstream is that when others do 'git fetch
origin', they'll also end up cloning those branches, and they'll live on
the others' local repositories until they decide to 'git remote prune'.
I think AGit workflow, or users' clones solves this problem better. HTH -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 "If I destroy you, what business is it of yours ?" (Dark Forest, Liu Cixin)
signature.asc
Description: PGP signature
