Stefan Beller <sbeller@xxxxxxxxxx> writes:
> On Mon, Oct 24, 2016 at 7:28 AM, Yash Jain <yashjain.lnm@xxxxxxxxx> wrote:
>> Hello,
>> I have two accounts on github("yj291197" and "yaki29").
>> Both the accounts have different gmail IDs("yj291197@xxxxxxxxx" and
>> "yashjain.lnm@xxxxxxxxx" respectively) but same passwords.
>> I used to use git for "yj291197" account and a few days earlier I made
>> this new account and used git commit to commit on "yaki29" but it
>> appeared as "yj291197" committed on "yaki29's" repo.
>> Then I pulled a request of that commit then it appeared "yaki29"
>> pulled a request with a commit of "yj291197".
>>
>> And during this whole session I was signed in as "yaki29" on github.com .
>>
>
> This is a Github issue, so ask Github support.
>
> Or read up on .mailmap files.
I am (obviously) not a GitHub support, but I think the confusion is
coming from not understanding who the committer and the author of a
commit are and where they are coming from. They are both recorded
locally, taken from user.name and user.email configuration variables
when the commits are made. "git push" to propagate them to GitHub
will NOT change these values of a commit, once a commit is created.
The story described looks quite consistent if the user has
yj291197@xxxxxxxxx configured as user.email and kept making commits
in the local repository, and pushed them to either yj291197 or yaki29
accounts at GitHub, without ever changing the local configuration to
use the other e-mail address. All commits would record the user and
e-mail address yj291197, and the only one that may be attributed to
the new one yaki29 would be the automerge created at GitHub when a
pull request is responded on-site without first fetching and making
a merge locally.