Github project import permissions are too aggressive
Description
While trying to import a Github project into Gitlab, I was met with the typical permissions screen advising me of what I'd be giving Gitlab access to:
These permissions are just too aggressive to justify, especially when you consider that I belong to a number of groups which have trusted me with write permissions:
- Read/write access to code, issues, pull requests, wikis, settings, webhooks & services, and deploy keys for all public and private repositories
Given that I'm only asking to import a single repo (hopefully to mirror it) it seems unreasonable to grant Gitlab permission to write deploy keys for unassociated projects.
Proposal
Reduce the permissions footprint to be repo-specific. Obviously, this is limited to whatever Github is allowing, so if this is not something Gitlab can fix, I'll understand.