Current behavior

During GitHub import, OneDev only auto-maps users for issue import (submitter, comments, assignees): it fetches the GitHub login's public profile email via the API and looks for a OneDev user with that exact verified email. If no match is found (e.g. no public email, or a users.noreply.github.com address), the submitter/commenter/assignee name is still imported as-is, but it's not linked to an actual OneDev user account. The login only ends up in a "non-existent logins" list shown to the admin — nothing else happens.

Feature request

Instead of only auto-matching and leaving unmatched logins as unlinked names, there should be a way to manually map the unmatched GitHub logins (currently ending up in nonExistentLogins) to a OneDev account after import — e.g. via a small mapping UI that lists exactly those logins and lets the admin pick a target user for each. This would solve the issue that noreply/private emails can never be auto-matched, especially annoying on large imports where many logins end up unlinked.