How to push to a non Samba Team member branch on gitlab ?

[Jeremy Allison]

On Thu, Nov 03, 2022 at 09:41:10AM +1300, Andrew Bartlett via samba-technical wrote:
>On Wed, 2022-11-02 at 13:24 -0700, Jeremy Allison wrote:
>> On Wed, Nov 02, 2022 at 01:22:02PM -0700, Jeremy Allison wrote:
>> > I'm working with a new contributor here:
>> >
>> > https://gitlab.com/samba-team/samba/-/merge_requests/2741
>> >
>> > and want to push a modified version of their patch
>> > that corrects some things to help them work with
>> > us here on the Team. Pushing to their branch
>> > helps them see what I corrected so is a very
>> > desirable thing to do.
>> >
>> > The gitlab page above shows their branch name as:
>> >
>> > vporpo/samba:master
>> ...
>> > git push gitlab +HEAD:vporpo/samba:master
>> >
>> > fails, as does:
>> >
>> > git push gitlab +HEAD:vporpo:master
>>
>> git push gitlab +HEAD:vporpo/master
>>
>> pushes, but not to MR 2741, so isn't
>> desirable :-(.
>>
>> > I can't see any logic or patterns in this, or am I just
>> > missing something about git (again).
>> >
>> > Jeremy.
>
>Sadly there isn't a way to change which branch a MR is for, you can
>however mention the old MR in the new MR which will trigger a
>notification.
>
>This is an unfortunate side-effect of the non-standard way we use
>GitLab, as the typical approach is to push back to their branch, as as
>it is typical the incantation is learnt earlier in the learning process
>(I've given that on the MR).

Thanks for the help Andrew, it is *much* appreciated.

git and gitlab are not always obvious :-).