On 2025-06-21, Andreas Enge wrote: > over the past few days I see branches pop up on the main Codeberg repo > that I think are pushed inadvertantly ... > For instance, ... > 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?
In the case of librecast-0.11.2, I intentionally pushed it in order to submit the corresponding (as yet unmerged) pull request: https://codeberg.org/guix/guix/pulls/665 I *could* use AGit workflow, and did for at least a few pull requests, but it was not my understanding that this was the *only* acceptible workflow... Pushing to a branch and making a pull request from a branch is a commonly used workflow, and it was my understanding that using conventional workflows was considered part of the advantage of switching to codeberg. I could also use my mirror of guix at https://codeberg.org/vagrantc/guix, but I was planning on deleting that since I am able to push to https://codeberg.org/guix/guix and codeberg is planning on moving forward with account size limits... although not all users would be able to push directory to branches on guix.git. I think we are still in an exploratory phase with switching to codeberg, so if using a different branch naming convention or something would help, or if there is an agreed upon (set of) acceptible workflow(s), or whatever, I would happily adjust. For the diffoscope and related updates: https://codeberg.org/guix/guix/pulls/561 I ended up in an odd situation where the branch name is diffoscope-298-signed, but the pull request is now updating to diffoscope 299 and a few other things ... so having a naming convention that is cleverer than what i've been doing (e.g. package-version) might be good idea. Or is there a way to change which branch a pull request is against? live well, vagrant
signature.asc
Description: PGP signature
