Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub thinks that Mergify rebases come from random users #5038

Closed
ulysses4ever opened this issue Sep 7, 2022 · 2 comments
Closed

GitHub thinks that Mergify rebases come from random users #5038

ulysses4ever opened this issue Sep 7, 2022 · 2 comments

Comments

@ulysses4ever
Copy link

ulysses4ever commented Sep 7, 2022

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
Copy link
Member

jd commented Sep 8, 2022

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

@ulysses4ever
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants