[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: maintaining lilypond git repository on github
From: |
Jonas Hahnfeld |
Subject: |
Re: maintaining lilypond git repository on github |
Date: |
Wed, 19 Aug 2020 08:48:27 +0200 |
User-agent: |
Evolution 3.36.5 |
Am Mittwoch, den 19.08.2020, 06:55 +0200 schrieb Werner LEMBERG:
> >> IIRC we talked about setting up automatic updates of
> >>
> >> https://github.com/lilypond/lilypond
> >>
> >> but it seems this is still missing. Is there any progress?
> >
> > If somebody grants me access to the repo, I can easily add a deploy
> > key with write access and setup mirroring from GitLab.
>
> I've sent a mail to Janek WarchoĊ.
>
> >> I've just updated it manually.
> >
> > Looks like the previous updates didn't purge removed branches, at
> > least there are still a bunch that are neither at Savannah nor
> > GitLab.
>
> I simply do
>
> git remote update
> git push --mirror git@github.com:lilypond/lilypond.git
>
> for manual updating... Shall I change this incantation?
Definitely add --prune to "git remote update" to remove branches that
ceased to exist on the remote. In general, I would not run the
mirroring from a real working copy of the repository because AFAICT git
push --mirror will also push local branches. But it doesn't really
matter if everybody is ok with me removing them once I get access.
> > I'd propose we delete all but the "protected branches" (GitLab
> > terminology; master, translation, stable/*, release/unstable)
> > because these are the refs that are going to be mirrored from
> > GitLab.
>
> Sounds sensible.
>
>
> Werner
signature.asc
Description: This is a digitally signed message part
Re: maintaining lilypond git repository on github, Jonas Hahnfeld, 2020/08/19