Author jeff.allen
Recipients bckfnn, jeff.allen
Date 2020-05-30.16:55:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I still find the GitHub user name wizard confusing, but I've got it to do something sensible (I think). Basically, it lets you substitute one email address for another in change sets.

It appears to list all the addresses it has found, whether it has identified the account or not, and so it is a lot of work to identify the ones that properly need a response. (I've done this.)  To identify the account correctly, the e-mail address has to be (in some sense) public in that account. Where it is not, there are three alternatives:

1. Choose an account, in which case the wizard will (most times) substitute a made-up address.
2. Supply an e-mail address you know it can correlate with the right account.
3. Leave it as it is, attributed to just the e-mail account.

Where the anomaly is the result of an obvious slip (e.g. jeff@localhost) alternative 2 seems sensible.

Where we can't reliably identify the committer with an account, I propose alternative 3. If they subsequently relate their account publicly with the address (verifiably to GitHub), I expect that to fix the problem.

The difficult case is where someone has used several addresses over time and not all are associated publicly with their account. All possibilities are open, but fortunately, where it matters for us, alternative 2 results in the same domain name, so we're not rewriting history too badly.

The result is:

Next I'll see if I can work with it, and if all seems ok, I'll repeat all this at  .
Date User Action Args
2020-05-30 16:55:02jeff.allensetmessageid: <>
2020-05-30 16:55:02jeff.allensetrecipients: + jeff.allen, bckfnn
2020-05-30 16:55:02jeff.allenlinkissue2892 messages
2020-05-30 16:55:02jeff.allencreate