Ludovic Courtès <l...@gnu.org> skribis: > Hello! > > Vagrant Cascadian <vagr...@debian.org> writes: > >> > git push --set-upstream origin vagrantc-test >> Enumerating objects: 44, done. >> Counting objects: 100% (44/44), done. >> Delta compression using up to 8 threads >> Compressing objects: 100% (10/10), done. >> Writing objects: 100% (35/35), 6.10 KiB | 6.10 MiB/s, done. >> Total 35 (delta 28), reused 32 (delta 25), pack-reused 0 >> remote: >> remote: Forgejo: User permission denied for writing. >> To codeberg.org:guix/guix.git >> ! [remote rejected] vagrantc-test -> vagrantc-test (pre-receive >> hook declined) >> error: failed to push some refs to 'codeberg.org:guix/guix.git' > > I have a lead: I wonder if being part of a team that has read-only code > access (all teams do) prevails over being a “collaborator” with write > access. > > https://codeberg.org/guix/guix/pulls/383#issuecomment-4974834 > > Could you check this hypothesis by removing yourself from the team(s) > you’re on (except “owners”)? > > Ludo’.
Hi Ludo. I tried removing myself from the lisp team to check your hypothesis. However it looks like I'm not a collaborator either anymore. I don't know if I clicked on the wrong "quit" button, or if my account was already not in the list of collaborators anymore for some reason and was just in the lisp team... Could you add back the "glv" account to the collaborators?
signature.asc
Description: PGP signature
