Dedicated admin account for gitlab imports
Migration of gitlab projects between different gitlab instances works by exporting it on the origin and importing it on the target instance. This MR is about migration toward gitlab.dune-project.org. During migration users (and thus issues, comments, MRs, ...) are matched them via their public e-mail address if the import is done via an admin account. However, this may fail in some cases:
- (a) User has not marked the e-mail address as public on the origin gitlab instance or uses a different e-mail address there.
- (b) User has not marked the e-mail address as public on gitlab.dune-project.org.
- (c) User is not registered on gitlab.dune-project.org.
While (a) can be handled by manually patching the e-mail address in the export file, there's no way to fix (b) and (c) if the users can no longer be reached. In such cases all contributions by the non-matched users are associated to the importing admin account. While this is highlighted in comments, it is not visible for MRs and issues.
It would be good to have a dedicated gitlab-import
admin account for this purpose. Then contributions of non-matched users could at least be identified as such and would not be associate to an admin account regularly used by a real person.