Comment

thebestaquaman@lemmy.world ⁨5⁩ ⁨days⁩ ago

Seriously: What kind of good options exist for migrating a couple GitHub repos (including CI pipelines that work across repos to deploy to azure) cleanly and quickly (i.e. including PR’s, issues, etc.) to a different provider?

source

Sort:hotnew top

fruitycoder@sh.itjust.works ⁨5⁩ ⁨days⁩ ago
Forgejo supports GitHub actions and of course git.

The forge metadata though? Like issues and such, are a harder problem to me

source
pinball_wizard@lemmy.zip ⁨3⁩ ⁨days⁩ ago
Here’s how I handled my migration to CodeBerg:

Code and history - add new remote, git pull and push. Done.

pull requests - were not an issue for me. I generally merge them or reject them same day, so I just migrated at the end of a day when none were open.

Issues - I just left the GitHub issue queue behind. It is a public archive now. I know where to find it to read it. Anything that matters will get a new issue at CodeBerg, someday.

CI/CD - I can’t comment. Mine are 95% bash anyway, so they should be easy to move, but I haven’t yet. My spicy take: most GitHub Actions are a hot mess, because they were written by folks not experienced enough to just use bash. Apologies to anyone who likes GitHub Actions. I’ve had mostly bad experiences with them.
source