5 ms·

In this case I think you could use a .mailmap [1] in the repo to associate the old email addresses with current, verified addresses. [1] https://git-scm.com/do

In this case I think you could use a .mailmap [1] in the repo to associate the old email addresses with current, verified addresses. [1] https://git-scm.com/docs/gitmailmap https://git-scm.com/docs/gitmailmap

nynyny7 5y ago
Interesting. One never stops learning new git features... However, while this works for git (i.e., maps old address to new address in "git log" for example), GitHub does not seem to honor this file.
- Kwpolska 5y ago
  GitHub bases the association of commits to user accounts on the list of e-mail addresses configured in the user’s profile: https://github.com/settings/emails https://github.com/settings/emails
- trulyme 5y ago
  Well, yes, but maybe they should? It doesn't seem like a huge feature...
  - leni536 5y ago
    Now which commit's mailmap file should be used for the association? Whatever is on the "default" branch currently?
    - Aeolun 5y ago
      Whatever is in the branch you are looking at? Seems fairly straightforward.
      - remram 5y ago
        Viewing a specific commit or viewing the repositories' statistics ("insights" tab) both have no attached branch.
        Cthulhu_ 5y ago
        in Github or in Git itself? While possible, I don't believe there's many floating commits around. The other issue of course is that at this point in time, there would not be a .mailmap. Of course, github can then fall back to a .mailmap file in the latest commit of the main branch.
        remram 5y ago
        Commits are not usually floating but are very commonly in more than one branch.
  - angus-g 5y ago
    What about if somebody clones a repo, then adds a .mailmap pointing all the addresses in the history to their own?
    - trulyme 5y ago
      If somebody clones the repo they can even rewrite history. But that is not the same as them being able to claim the ownership of a commit in the original repo.
    - teawrecks 5y ago
      Then in their clone, they made all the commits. But who cares about their clone?

nynyny7 5y ago

Interesting. One never stops learning new git features... However, while this works for git (i.e., maps old address to new address in "git log" for example), GitHub does not seem to honor this file.

Kwpolska 5y ago
GitHub bases the association of commits to user accounts on the list of e-mail addresses configured in the user’s profile: https://github.com/settings/emails https://github.com/settings/emails
trulyme 5y ago
Well, yes, but maybe they should? It doesn't seem like a huge feature...
- leni536 5y ago
  Now which commit's mailmap file should be used for the association? Whatever is on the "default" branch currently?
  - Aeolun 5y ago
    Whatever is in the branch you are looking at? Seems fairly straightforward.
    - remram 5y ago
      Viewing a specific commit or viewing the repositories' statistics ("insights" tab) both have no attached branch.
      - Cthulhu_ 5y ago
        in Github or in Git itself? While possible, I don't believe there's many floating commits around. The other issue of course is that at this point in time, there would not be a .mailmap. Of course, github can then fall back to a .mailmap file in the latest commit of the main branch.
        remram 5y ago
        Commits are not usually floating but are very commonly in more than one branch.
- angus-g 5y ago
  What about if somebody clones a repo, then adds a .mailmap pointing all the addresses in the history to their own?
  - trulyme 5y ago
    If somebody clones the repo they can even rewrite history. But that is not the same as them being able to claim the ownership of a commit in the original repo.
  - teawrecks 5y ago
    Then in their clone, they made all the commits. But who cares about their clone?