1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.EMACSE

  • Salsa permissions

    From Aymeric Agon-Rambosson@21:1/5 to All on Mon Mar 4 20:30:01 2024
    Hello everyone,

    I have packaged new releases of various packages like transient,
    magit and with-editor, and I'd like to be able to push them.

    However, some branches in those repos are protected, so I cannot
    push to them, since I am developer in the Emacsen Salsa group.

    May I become a maintainer in the Emacsen Salsa group ?

    Best,

    Aymeric

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aymeric Agon-Rambosson@21:1/5 to All on Sun Mar 10 17:50:01 2024
    Hi Xiyue,

    Le lundi 4 mars 2024 à 11:38, Xiyue Deng <manphiz@gmail.com> a
    écrit :

    Will you submit the changes as merge requests for review? I'll
    try to
    take a look later this week.

    I generally don't submit merge requests when I package a new
    upstream release, since it requires synchronised pushes to
    multiple branches (upstream branch, debian branch, according to
    the git workflow of the repo). And this, as far as I know, is not
    supported by gitlab merge requests.

    But, if you want, as soon as I get the right to push, and do so, I
    can ping you for review before asking for an upload.

    If you do not want to wait, I can also prepare private forks of
    the repos I mentioned.

    Do tell me.

    Cheerio,

    Aymeric

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aymeric Agon-Rambosson@21:1/5 to All on Mon Mar 11 21:30:01 2024
    Hi Xiyue,

    Le dimanche 10 mars 2024 à 18:08, Xiyue Deng <manphiz@gmail.com> a
    écrit :

    For getting push rights you'll need to wait for the team owners'
    approval.

    Yes, this is what I'm doing.

    I don't think I have permission to add new members to the
    team

    No. And I do not need to be added to the team, I am already in it.

    but I do have commit rights to handle merge requests, which is
    why
    I asked.

    Unless I'm mistaken, not in this case.

    The branches I want to push to are protected, which means neither
    of us (we are "Developers", in gitlab permission parlance) can
    push to it. Only "Maintainers" or above can.

    This is why I'm asking to be promoted to gitlab Maintainer. It is
    the first time I want to push to protected branches. Those are not
    very frequent, as far as I can tell, and I am not sure whether
    they were declared protected on purpose or simply by default.

    Best,

    Aymeric

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sean Whitton@21:1/5 to Aymeric Agon-Rambosson on Tue Mar 12 03:50:01 2024
    Hello,

    On Mon 04 Mar 2024 at 08:17pm +01, Aymeric Agon-Rambosson wrote:

    Hello everyone,

    I have packaged new releases of various packages like transient, magit and with-editor, and I'd like to be able to push them.

    However, some branches in those repos are protected, so I cannot push to them,
    since I am developer in the Emacsen Salsa group.

    May I become a maintainer in the Emacsen Salsa group ?

    I'd prefer just to unprotect the branches.

    Does anyone have a script which mass-unprotects branches?

    --
    Sean Whitton

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmXvvpYZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQA3UEACHC7ZhivDkECWH8+Y8FmG+ rTds2tVlRPawHyoWQnoyhFh19lL3++kF+Mdp5c6+V7BGWRHRSgRnNEYd7uEcBGHv V8Do6XVLMR+Wcpac3OzAwqCQdEIZ51he70BPYotliG2blmj+2d7BIhsRHB0lMFV9 clmF4G9XqCfa4js8KwbLc4VxqnEsfMFfS0COELqMfcI1hU47HqW8vMWACNB2wcBR uzTMhqNG4WgtzLUtpJdcHi2R4HrHpKirym8Kl1tpjS7ETK95hAU3xtyyMscGVrsd pj18PjjaYX/BH24Yt0TBrnwnpozIogAJfssP0JszYvEmcqBXCxPQskdwNN5Guljv lDH61EqC5tDsOYQJC+ViBQU0yysiCHOUuLeNdyk5nxdFq1smpvxiS/xsh3ydL/VV Hw7lrQqQFfTBQ7M5Bhs6JHlU45pY7VES50OsyH+p2inMFdIxXxEwWxt4s03g2Nte 8ncQwlo4Cczx8pidfiwxHcoJNt9xv0Akl5fBIUn38VaDMUCsSxFktxyJa2iQhvjA 47beStCmqIh9YqOzyRegQxVfgDjl0FrdFVKIXsyePhsTdkXuF8N34lUITmO9jwYh f7v0xhzuCdob8KsUtZnWIgFKpNKWxBRr3bI5S6ObYGntHppsAE/VEdNlmsslZTUW 5U0pvY6GfwCEaFJ+oxPI0w=ÿVV
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usen
  • From Sean Whitton@21:1/5 to All on Tue Mar 12 15:30:01 2024
    Thank you very much, I'll try running this soon.
    --
    Sean Whitton

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sean Whitton@21:1/5 to Aymeric Agon-Rambosson on Tue Mar 26 14:30:01 2024
    Hello,

    On Tue 12 Mar 2024 at 12:29pm +01, Aymeric Agon-Rambosson wrote:

    Hi Sean,

    Le mardi 12 mars 2024 à 10:31, Sean Whitton <spwhitton@spwhitton.name> a écrit
    :

    I'd prefer just to unprotect the branches.

    Agreed.

    Does anyone have a script which mass-unprotects branches?

    I just looked it up, I came up with the following scripts. You need to have created an API token with the relevant permissions. And the scripts use the ~jq(1)~ command, installable from the homonymous debian package.

    The attached file ~debian_emacsen_ids_and_branches~ contains the project ids and the names of the protected branches of the debian-emacsen group. I generated this list using the scripts ~salsa_fetch_debian_emacsen.sh~ and ~salsa_list_protected_branches.sh~, which I have included for reference.

    The script ~salsa_unprotect_branches.sh~ does the actual unprotecting. I could
    not test it, for I am not the owner (I get 403 errors, which makes sense).

    Here are the relevant gitlab api documentations I used to get to this : https://docs.gitlab.com/ee/api/groups.html and https://docs.gitlab.com/ee/api/protected_branches.html.

    Do tell me how it worked, I am curious.

    Xiyue reports it worked :)

    --
    Sean Whitton

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmYCy8oZHHNwd2hpdHRv bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQBxYD/0apJBI4Zo/P2XER3H/g+Ov wbJQj3K6Ref0Z8biPzYEboNjjTy7loQvKOvYD8292YLMAZus8UbUeq3IAYeeebWU tePMLL3s807j0imEYqrZPONNisONvg92i/m0/CSPht8c/oCzMEvvJmRFFd0ENfVp dD+BiaUmQPWNOvZTurmi/dhoHYnyYgUTZBqiQmhrOfmJmhoDvVPjnkuOFqCJZzrv 9vYmcj3d489vzQVK/HnSlaerrudmKjei3DDVQcgq7Wpo2gcry1La2nOUAhCGouhf oZl9lE9nAh3L12TxlLDtQlM/yO42uN5slwUZVA+hZCYqOwlmLIxASyc7o85dGHBL hW9rcsb5c/ZOjpN7VFpf9TnxsENiRYa9kuirLeZa6bfD5SGmQEocsizNLSmNWxi2 /idwzyW9tEUmpaJ2U0wcT003kmOmT0vl45X3A3FDUIaVrcDnVQPAKgThvqHAdNh5 G1IcgJL4IQ/Z034El34RDfUGBl7HE42OOQE+dzzgEHRSWzhDAbsVnWNYxaOBdd0R Jl9ui/ZD/TSdoeE1SVh2iI/uDJW5fFIsUoiuy5DgjMt4oYW9522aCZuxqZES3T5X RLPUJV86/wmXbDri9UGQhyu3hBzCTG5n9w/j47xxzAskRdW0GMDiauYvqhxdrTeW 4z7+GXnkRUz5gPp94154kA==FVSD
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Us
  • From Aymeric Agon-Rambosson@21:1/5 to All on Tue Mar 26 20:20:01 2024
    Le mardi 26 mars 2024 à 21:21, Sean Whitton
    <spwhitton@spwhitton.name> a écrit :

    Xiyue reports it worked :)

    Thanks a lot !

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)