Re: want to help

[Jean Abou Samra]

Hi David,

As written privately, please try to write from your address that
is subscribed to this list (dsz@dedekind.net) or to subscribe this
one. Otherwise, each of your messages needs to be manually approved
by Mark or me and doesn't reach the list before this.


Le 18/01/2023 à 00:45, David Zelinsky a écrit :
> Jean Abou Samra <jean@abou-samra.fr> writes:
>
> > Here is what the contributor's guide has to say on commit access:
> >
> > https://lilypond.org/doc/v2.24/Documentation/contributor/commit-access
> >
> > “Generally, only contributors who have already provided a number of
> > patches which have been merged to the main repository will be considered
> > for membership.”
> I did read that in the contributor's guide, and initially assumed by
> "main repository" it meant "master branch" (though why wouldn't it say
> that?).



The "main repository" is https://gitlab.com/lilypond/lilypond

When we talk about it, it is often in contrast to your
personal fork of the repository, which will be
https://gitlab.com/your-gitlab-username/lilypond
as soon as you create it. See

https://lilypond.org/doc/v2.25/Documentation/contributor/cloning-and-forking-the-repository



> But when I go to the Merge Requests page there is no "New Merge
> Request" button as the gitlab docs say there should be.


For me, there is ... See the screenshot attached.


> Moreover, when
> I try to commit my local branch (to a branch named dev/... per
> instructions), it refuses to let me:
>
> ------------
>
> % git push gitlab defineBarLine-doc:dev/expand-defineBarLine-documentation
> remote:
> remote: ========================================================================
> remote:
> remote: ERROR: You are not allowed to push code to this project.
> remote:
> remote: ========================================================================
> remote:
> fatal: Could not read from remote repository.
> Please make sure you have the correct access rights
> and the repository exists.
>
> ------------
>
> I have "gitlab" correctly configured to point to the LilyPond gitlab
> project---I can pull from it.  And I have an ssh key set up, and checked
> that I can push like this to a different project that I own.
>
> What am I missing??


The fork step. You cannot push to the main repository while you
don't have commit access, so you need to fork it, making a copy
of it into your own GitLab namespace (gitlab.com/your-username).
You can then create a merge request from a branch on your fork
to the master branch from the main repository.

When you get commit access, you can push your branches directly
to the main repository instead of your fork, but I would still
recommend the fork, and this is what I do myself.

Best,
Jean

Capture d’écran du 2023-01-18 01-03-12.png
Description: PNG image

OpenPGP_signature
Description: OpenPGP digital signature