know estimate of time remaining to complete an import, and option to cancel it #723

I started importing a github repo 3H ago, and the import is still running, no idea how much more time it will take.
I'd bet the thing is stuck... and would like to know if it really is, and if yes, or if too much time is required, how to cancel it, so that instead I could just git push instead (I'm pretty sure it will take a lot less time).

Imports are restricted by the API rate limits of external platforms (e.g. GitHub, GitLab). It's really hard to tell.

Improvements are hard as long as proprietary platforms enjoy you are vendor locked and don't want you to move away. Gitea is working on restoring GDPR data dumps instead, which might be a good option for the future.

Having a more verbose log of what the migration tool is actually doing might be worth a further look, though.

@fnetX is there a gitea-related issue on that? (Couldn't find one during a quick search.)

I have created a new "Find-grained personal access token" on GitHub and started a migration of a GitHub repository to Codeberg. 20+ minutes later, the token is still listed as "never used" on https://github.com/settings/tokens?type=beta

So it looks not like rate limiting on the GitHub side, but the migration getting stuck in some job queue of Codeberg.

So it looks not like rate limiting on the GitHub side, but the migration getting stuck in some job queue of Codeberg.

Keep in mind that these situations are very context-specific and change super fast. The job queue of Codeberg may play a role now, but it may not have played a role with OP's problem.

I would suggest opening a new issue for this using "Reference in a new issue" and that we open a new Gitea issue for what fnetX suggested as well. (I can't do this right now.)

I suppose that the access token is not used while cloning the Git repo itself, only for accessing the metadata like issues, releases etc.

Also note that the rate limiting is not imposed per token but per IP address, thus applies to Codeberg as a whole, and yes it sometimes does impact the Git cloning, too. (Not always, though)