Is Repository Mirroring Broken?

[daskol]

It seems that the latest commit has different checksums in GitLab and GitHub.

commit 530b50da85059e9666b49e2d00597b28e5f43b60  # GitLab
commit 72f44fa1cb657504aea3d1c6927262d18715f2ef  # GitHub

    darts: not adding pointers when a data is only used in W + ignore data only...

Moreover, CI statuses in GitLab and GitHub differ too! GitHub CI is green while GitLab one is not!

[sthibaul]

It seems that the latest commit has different checksums in GitLab and GitHub.

This is unfortunately expected: in the gitlab repository there is a big commit that github refuses to take. We thus have to live with different histories :/

This doesn't prevent us from taking pull requests, by cherry-picking.

Moreover, CI statuses in GitLab and GitHub differ too! GitHub CI is green while GitLab one is not!

The github CI is much more limited that the gitlab CI.

[daskol]

But what about contributing guidelines? I cannot find any instructions.

This is unfortunately expected: in the gitlab repository there is a big commit that github refuses to take. We thus have to live with different histories :/

These ones?

$ git log --find-object=b52e7f818749
commit 45966c3b35fa42e36baa7af268538ec32d995526
Author: Andra Hugo <andra.hugo@inria.fr>
Date:   Tue Oct 11 10:00:51 2011 +0000

    forgot some small things

commit 8d1d5c0a77ba5b8b7ee44969dfbdfed0c11b9eef
Author: Andra Hugo <andra.hugo@inria.fr>
Date:   Tue Oct 11 09:57:32 2011 +0000

    modified benchs in order to avoid duplication, manag concurency of add/remove workers to/from ctx, hypervisor manages the resize of ctxs

Why just not filter history and create a new repo? The existing one could be archived then.

[sthibaul]

But what about contributing guidelines? I cannot find any instructions.

There's not much more to say than what readme says: contributions are welcome both on github and gitlab :)

Why just not filter history and create a new repo?

It'd mean rebasing the git history for all the current gitlab contributors.

[daskol]

There's not much more to say than what readme says: contributions are welcome both on github and gitlab :)

It is unclear how to pass CI check and where to discuss contributions. It is more convenient for me to submit PR on GitHub rather than your own GitLab installation.

It'd mean rebasing the git history for all the current gitlab contributors.

Then may be git-replace solves the issue? You could keep entire history on GitLab and recent commits on GitHub as an example.

[nfurmento]

Hello You can find instructions here <https://starpu.gitlabpages.inria.fr/involved.html> Nathalie Le 3 juin 2024 12:20:53 GMT+02:00, Daniel Bershatsky ***@***.***> a écrit :

…

> There's not much more to say than what readme says: contributions are welcome both on github and gitlab :) It is unclear how to pass CI check and where to discuss contributions. It is more convenient for me to submit PR on GitHub rather than your own GitLab installation. > It'd mean rebasing the git history for all the current gitlab contributors. Then may be `git-replace` solves the issue? You could keep entire history on GitLab and recent commits on GitHub as an example. -- Reply to this email directly or view it on GitHub: #49 (comment) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>