First, they restricted code search without logging in so I’m using sourcegraph But now, I cant even view discussions or wiki without logging in.

It was a nice run

      • Scrubbles@poptalk.scrubbles.tech
        link
        fedilink
        English
        arrow-up
        6
        ·
        9 months ago

        It’s more I don’t have them all checked out, and a good chunk are mirrors of github, so I’ll have to list out each one and push to a new remote, mirrors will have to be setup again, and I also use the container and package registries. I’m pretty embedded. It’s not impossible, but it’s a weekend project for sure.

        • zeluko@kbin.social
          link
          fedilink
          arrow-up
          3
          ·
          edit-2
          9 months ago

          If it was just forked, cant you just switch the package/container-image and be done?

            • StarDreamer@lemmy.blahaj.zone
              link
              fedilink
              English
              arrow-up
              2
              ·
              9 months ago

              Simply changing the binary worked for me. Been more than 1 month and no migration issues.

              It does still show gitea branding, however.

            • PowerCore7@lemm.ee
              link
              fedilink
              arrow-up
              1
              ·
              9 months ago

              If you are using containers, it should be fairly trivial. Otherwise, there might be some renaming to do, but Forgejo should be 100% compatible with Gitea (at least right now). Just make sure you have a good backup in case anything would happen.

    • lambchop@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      My understanding is the fork isn’t doing much but waiting to see if gitea turns to shit, pushing all their changes upstream. If you use docker I’ve heard you can just pull the new image and it simply drops in, no migration needed.