Near-daily "Remote mirror update failed" e-mails from GitLab
Sebastian Graf
sgraf1337 at gmail.com
Mon Apr 15 20:08:42 UTC 2019
Hey,
sorry, I'm a little late to respond. I didn't push to GitHub, at least not consciously.
Let me know if you find that I screwed up somewhere.
Cheers,
Sebastian
________________________________
Von: Ben Gamari <ben at well-typed.com>
Gesendet: Samstag, April 6, 2019 8:28 PM
An: Ryan Scott; Sebastian Graf
Cc: ghc-devs at haskell.org
Betreff: Re: Near-daily "Remote mirror update failed" e-mails from GitLab
Ryan Scott <ryan.gl.scott at gmail.com> writes:
> Almost every day now I receive an e-mail from GitLab titled "Remote
> mirror update failed", which contains something like:
>
> To
>
> ! [remote rejected] wip/dmd-arity -> wip/dmd-arity (cannot
> lock ref 'refs/heads/wip/dmd-arity': is at
> e1cc1254b81a7adadd8db77c7be625497264ab2b but expected
> f07b61d047967129a3ae0c56f8894d41c5a9b036)
>
> error: failed to push some refs to '[FILTERED]@github.com/ghc/ghc'
>
Hmm, how annoying. Strangely, the `wip/dmd-arity` branch currently
appears to be sitting at the same commit on GitLab and GitHub so I'm not
really sure what to do here.
sgraf, did you ever push a branch manually to the github.com/ghc/ghc
mirror?
Cheers,
- Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20190415/74cac5c7/attachment.html>
More information about the ghc-devs
mailing list