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

  • @[email protected]
    link
    fedilink
    1495 months ago

    Just so you’re aware, Gitea was taken over by a for-profit company. Which is why it was forked and Forgejo was formed. If you don’t use Github as a matter of principle, then you should switch to Forgejo instead.

    • Scrubbles
      link
      fedilink
      English
      545 months ago

      Damnit of course it was. Thanks for letting me know, now I’ll have to redo my 100+ repos.

        • Scrubbles
          link
          fedilink
          English
          65 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
            link
            fedilink
            3
            edit-2
            5 months ago

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

            • Scrubbles
              link
              fedilink
              English
              25 months ago

              Depends on how much it was changed I’m guessing. Fingers crossed I could just flip it over, but who knows

              • StarDreamer
                link
                fedilink
                English
                25 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.

              • @[email protected]
                link
                fedilink
                15 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.

      • @[email protected]
        link
        fedilink
        15 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.

    • @Hexarei
      link
      25 months ago

      Oh man, thanks for this. I had no idea, having used gitea for years now.