-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing many cards to a new GitHub repo triggers abuse detection #5
Comments
I haven't really used this in a while, so correct me if I'm wrong but I think that the |
Oh good point, I didn't try that. I ended up doing the rest manually, fortunately it only skipped my archived cards. Thanks for the advice though. Is this using an oauth token or key that gives it the more relaxed rate limiting? If not, it would help. |
it doesn't, but it tracks the cards that've already been imported so should start from where the last card failed |
My problems are resolved anyway since I finished my only import. Want to leave this open or close it and have people use |
Yeah; it's certainly not resolved. Potentially I should force |
Unfortunately I don't seem to be able to give a different kind of token to prevent this, and because issues can't be deleted I'll have to do the rest of my import manually.
The text was updated successfully, but these errors were encountered: