Mergifyio / mergify

Mergify Community Issue Tracker
https://mergify.com
Apache License 2.0
318 stars 91 forks source link

GitHub thinks that Mergify rebases come from random users #5038

Closed ulysses4ever closed 1 year ago

ulysses4ever commented 1 year ago

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.

2022-09-07_09-09-1662558014

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

  1. Open a PR.
  2. Wait until the target branch (e.g. master) goes ahead.
  3. Explicitly ask Mergify to rebase or satisfy the Mergigy conditions for a merge.
  4. Watch a GH message in the style: X forced-pushed the Y branch from Z1 to Z1 A hours ago. Where X is a random user.

Specifications

jd commented 1 year ago

This is documented in our FAQ, but I admit it's a not visible for rebase. I'll update our docs.

ulysses4ever commented 1 year ago

Oh, I'm sorry for missing it in the docs. Thanks a lot for pointing me to the right place!