#Forgejo keeps impressing. Migrating a larger repo with lots of issues etc, only took the creation of an access token. Once again, i’m super happy with my decision to selfhost my #git.
#selfhosted #opensource #devops
https://docs.codeberg.org/advanced/migrating-repos/#migrating-from-services
how does it deal with all the user names, e.g., in the issues? does it create ghost users, unlinked names or links to their respective GitHub pages?
you end up with something like this:
oXXXXXXXd commented last year (Migrated from github.com)
so you get the github username, but that’s it.
ah, thanks. i guess just linking to the GitHub user page would be sufficient as acknowledgement. on the other hand, as long as you keep the GitHub repo, that would not be an issue anyway.
ghost users would be a terrible idea, as it would just fill your server with garbage xD (have that problem with another program)
To be fair it’s only the name. The only link is to github, rather than the user profile.
What I liked the most from it is the inclusion of releases on the migration.
haha. I missed that. Thank you. I was so stoked about the issues 🤪
Sad I lost access to GitHub account due to their dumb 2FA enforcement.
I miss the auto tagging columns in kanban…
Are you using a CLI?
No. I started that way, but realized I could keep the issues, etc, by using the web “new migration” feature.
I meant for cloning and such. It’s been the biggest pain point for me, especially having to manage multiple accounts
I don’t think that’s exposed via the cli. That would also be my preference.
