When Mergify needs to rebase before merging, I expect that newly-created commits are authored by the same person who authored original commits of the PR. Maybe, co-authored by Mergify (not sure about that). And that info is correctly reflected on GitHub.
Expected Behavior
When Mergify needs to rebase before merging, I expect that newly-created commits are authored by the same person who authored original commits of the PR. Maybe, co-authored by Mergify (not sure about that). And that info is correctly reflected on GitHub.
Actual Behavior
What I see on GitHub is stunning, e.g.
source PR is here
So, the commits have the right authors, but the message that GitHub produces mentions a random user (who even gets a notification about it iirc).
Another, smaller example, without an explicit request to rebase is here: the author is GH user coot, but in one of the rebase messages we see the GH user andreabedini.
Steps to Reproduce the Problem
master
) goes ahead.X forced-pushed the Y branch from Z1 to Z1 A hours ago
. Where X is a random user.Specifications