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.techEnglish
      6·
      10 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
        3·
        10 months ago

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

          • StarDreamer@lemmy.blahaj.zoneEnglish
            2·
            10 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
            1·
            10 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.