Improve migration documentation #35

(withing UI and/or as part of documentation?)

We have seen some reports of people having trouble migrating their repos to Codeberg, one example here: https://mastodon.technology/web/statuses/104734974106405778

We might potentially improve the process by adding some clear explanations how to avoid pitfalls.

Relevant discussion for improving import UX: go-gitea/gitea#9096 (comment)

A new import UX was merged! (go-gitea/gitea#12619)
new import UX

What parts of the migration process would need documentation?

Most troubles seem to be caused because it is not intuitive to fill in the API access token.

(one example in the mastodon conversation linked above)

Gitea 1.13 would solve this, though it would still be nice to have a guide.

Would it be okay to wait until Gitea 1.13 is deployed at Codeberg and to then add an article about migrations, maybe to Getting Started?

That way we wouldn't have to write and then re-write that article.

Sounds good to me.

No longer blocked, we are even awaiting 1.14 :-)

!139 now covers migrating between Gitea and Gitea, we should still elaborate a bit on migrating from other platforms to Codeberg, especially from GitHub as this seems to have some more caveats like rate-limiting etc.