help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: gitlab out of sync with sourceforge and github repositories
Date: Mon, 19 Dec 2022 00:40:37 +0100	[thread overview]
Message-ID: <11280-1671406837.269946@cXxL.OsDz.ZHWK> (raw)
In-Reply-To: <bc9307eb-bab4-4b26-900b-8fe2bb6a2270@app.fastmail.com>

"Daniel Shahaf" wrote:
> I'm not sure what does the pushes.  It doesn't seem to be documented in
> the infra repository either.  Oliver, any idea why gitlab hasn't updated in 4.5 days?

It was configured so as to happen automatically. Looking now, under
Settings→Repository→Mirroring repositories, everything appears blank and
the only Mirror direction offered appears to be "Push". Documentation
also appears to mention that pulling is an Ultimate only feature. It may
have only stopped now because you logged in.

There is a programme to allow open source projects to apply for that for
free, see: https://about.gitlab.com/solutions/open-source/join/

However, I'm more inclined to delete the (now broken) mirror than jump
through their hoops.

I only ever fetched from it to get at the merge requests. A slight lag
is not something I'd ever be especially concerned about. There have only
been 16 merge requests. If we just want the extra backup, there are
other options like codeberg and bitbucket.


  reply	other threads:[~2022-12-18 23:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 13:47 Jim
2022-12-15 19:01 ` Jim
2022-12-15 21:26   ` Daniel Shahaf
2022-12-16 21:04     ` Jim
2022-12-17 19:57       ` Bart Schaefer
2022-12-17 20:14         ` Daniel Shahaf
2022-12-18  1:58           ` Jim
2022-12-18 19:42             ` Daniel Shahaf
2022-12-18 23:40               ` Oliver Kiddle [this message]
2023-03-06 13:42                 ` Jim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11280-1671406837.269946@cXxL.OsDz.ZHWK \
    --to=opk@zsh.org \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).