As already hinted at in the introduction, the differences in user identity handling between Git and Darke is a key point in this integration.
Git uses a user name and an email address to uniquely identity the person who committed a change. Darke replaces that with a Darke identity which specifies your username and Darke server in the same way an email address does. (Darke in general tries to stay away from using email for anything.)
I have implemented the options to generate such a mapping file and use it during the import process. By default
darke.invalid is used as the Darke server. (That host will be handled specially in the UI.)