Re: repository at GitLab

[David Kastrup]

David Kastrup <address@hidden> writes:

> Jonas Hahnfeld <address@hidden> writes:
>
>> Am Montag, den 11.05.2020, 12:44 +0200 schrieb David Kastrup:
>>> Jonas Hahnfeld <address@hidden> writes:
>>> > Am Montag, den 11.05.2020, 11:42 +0200 schrieb David Kastrup:
>>> > > Jonas Hahnfeld <
>>> > > address@hidden
>>> > > > writes:
>>> > > > Everything went pretty much as expected, so here's the repo:
>>> > > >           
>>> > > > https://gitlab.com/lilypond/lilypond
>>> > > > 
>>> > > > If you already have a local repository cloned from Savannah, execute
>>> > > >  $ git remote set-url origin 
>>> > > > address@hidden
>>> > > > :lilypond/lilypond.git
>>> > > > to switch to GitLab (or edit your .git/config manually if preferred).
>>> > > 
>>> > > Wouldn't that just be readonly access?
>>> > 
>>> > It has updated both for me, probably because I used SSH for both fetch
>>> > and push.
>>> 
>>> dak@lola:/usr/local/tmp/lilypond$ git push -o merge_request.create
>>> -o merge_request.target=staging -o merge_request.title="Issue 5965"
>>> origin issue5965:issue5965
>>
>> Interesting, didn't know about this possibility...
>
> The funny thing is I don't know about any other possibility.  Web
> interfaces are not really my thing, and this is what I found when
> grasping around.  I now try figuring out where my merge request ends up
> and how it can be found and treated from the web interface.
>
> It probably should be a project-wide setting to have
> merge_request.target=staging as default?
>
>> Just added you (and all others that were in lilypond-trial) to the
>> lilypond group.
>
> Thanks.

And actually, I don't know what the workflow right now is and whether I
even was supposed to push something to the central repo to get it (back)
under review.  This was basically just me prodding the repo for lack of
any other idea of how to interact.  I know now how to do one thing.  I
just don't know whether this is what I am supposed to be doing.

-- 
David Kastrup