3.1.3 Cloning and forking the repository

Clone the LilyPond repository to get the source code and its history:

git clone git@gitlab.com:lilypond/lilypond.git

New contributors need to fork it in order to push branches. Using a fork is no longer necessary (but may be convenient) when you are given developer access. Visit https://gitlab.com/lilypond/lilypond and press “Fork” on the top right. After the fork is created, set up a new remote:

cd lilypond
git remote add fork git@gitlab.com:your-username/lilypond.git

To list remote repositories that are configured, along with their URLs:

git remote -v

You should have origin pointing to the official LilyPond repository, and fork pointing to your your private fork.