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

you are viewing a single comment's thread
view the rest of the comments
[–] 54 points 2 years ago (8 children)

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

  • source
  • parent
  • hideshow 8 child comments
  • [–] 18 points 2 years ago (5 children)

    Changing the remote should be fairly trivial with enough bash skills

  • source
  • parent
  • hideshow 5 child comments
  • [–] 6 points 2 years ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago* (3 children)

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

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 years ago (2 children)

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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 years 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.

  • source
  • parent
  • [–] 1 point 2 years 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.

  • source
  • parent