-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to aggregate developers when using .mailmap or --people-dict #355
Comments
Thanks for digging this @Code0x58! Yes, merging several signatures with It would be awesome if you PR your findings to the README 👍 Besides, I am happy to include the script that you crafted to convert |
Now I'm familiar, I can see I misinterpreted the documentation about being able to have multiple emails mapping back:
So in #356 I extended the
As for converting a mailmap to a |
Signed-off-by: Oliver Bristow <[email protected]>
Signed-off-by: Oliver Bristow <[email protected]>
Signed-off-by: Oliver Bristow <[email protected]>
Hi. Looks like there is an error in this code:
This gives an index shift by 1 between This should fix an issue
|
When using just a committed
.mailmap
the aggregation is done nicely, but when--people-dict=...
is added the mailmap is not used at all. This is due to the branching ininternal/plumbing/identity/identity.go
and lack of handling of mailmap in theIdentityDetector.LoadPeopleDict(...)
.Another issue is that if you do use input to
--people-dict
which has multiple emails mapping to the same name, those results will not be aggregated. I believe this is down to this method which doesn't check for duplicateids[0]
before appending. A workaround (or intended but not clearly documented way) for this is to roll any duplicates into the same line e.g.To work around the mailmap not being used, you can convert your mailmap into a
--people-dict
and pass that.The text was updated successfully, but these errors were encountered: