You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What do you think of the idea of the parsed .mailmap file from the repos (if there is one) being represented by a queryable table in MergeStat?
This would allow constructing a query to identify all email addresses of contributors that have not been assigned a canonical name through the .mailmap file.
The text was updated successfully, but these errors were encountered:
I think that could make sense - so something like SELECT * FROM mailmap('mailmap-file-contents') which would return rows of "proper" name/emails and their corresponding values to match on
Yes, SELECT * FROM mailmap('path/to/repo') might be even easier to use, if we assume the convention that a .mailmap file (if there is one) is included in the repo root.
What do you think of the idea of the parsed
.mailmap
file from the repos (if there is one) being represented by a queryable table in MergeStat?This would allow constructing a query to identify all email addresses of contributors that have not been assigned a canonical name through the
.mailmap
file.The text was updated successfully, but these errors were encountered: