• jonne@infosec.pub
      link
      fedilink
      English
      arrow-up
      8
      ·
      edit-2
      2 years ago

      Yeah, the code history is the easiest thing to migrate. The other stuff like issues relies on having a good exporting/importing tool on both sides.

  • tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    1
    ·
    edit-2
    2 years ago

    Ooh, I didn’t know that someone had developed a mechanism to move issues and PRs.

    I remember commenting on the fact that while it’s easy to move the source repo itself from location to location, as git makes that easy and self-contained, issues and PRs didn’t enjoy that.

    • marsokod@lemmy.world
      link
      fedilink
      English
      arrow-up
      16
      ·
      2 years ago

      You can easily do that with forgejo/gitea. However, you cannot sync these issues, that’s a one-off operation.

      You can however totally sync the git repo - either out of the box or using web hooks/git hooks.

      • Chris@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 years ago

        I bet you could sync issues if you were bored enough. It’d be a pipeline that you have to maintain and two way syncs are a pain to maintain, but I bet it’s doable

    • pressanykeynow@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      2 years ago

      It probably won’t, they were banned due to sanctions that the EU completely support. Though they were unblocked so it raises questions was the ban even legitimate and also why it took 2 weeks to unban them.

      Edit. Also will it be as easy to organize ban of other services by making a commit with Russian vpn?

  • MinFapper@startrek.website
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    20
    ·
    2 years ago

    It doesn’t seem like a very “walled” garden if they were able to migrate all their data including issues and comments