<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=31215) </details> <!--IssueSummary end--> When importing repositories from GitHub or BitBucket, the git part is the easiest and fastest step. If the project has a long history of collaborations on the platform, pulling all related data is subjected to API rate limits. This may lead to long hours of waiting. We may have a few alternatives here to improve the overall experience: 1. surface when we are rate limited, so people know "who to blame" 1. just after we imported the repository, allow the user to see it (probably is a good idea to keep it 'read-only' so we don't break or make the import code too difficult, like trying to import a commit discussion, while the user just forced pushed and removed that comment) 1. keep all other interactions read-only, until you can finish the import completely We currently have only one read-only flag on the project, and I believe it only affects the repository, not issues or merge requests, so we should probably add another one for those other places. Discussion on hacker news: https://news.ycombinator.com/item?id=20768035