Merge commits done using pull-requests are showing the wrong author(BBS-73513)

Issue #15798 closed
Gabriel Marcolino
staff created an issue

Commits are currently inheriting the user who was the author of the commit or pull-request, not the user who actually did a pull-request merge and created that new commit.

Pipelines builds are picking up the right user, the one who actually Merged the pull-request and thus fired a webhook, however, this is causing a mismatch between the information on the commit page and the build status page regarding who is the Author of the commit.

eg.

Screen Shot 2018-03-07 at 13.37.19.png Screen Shot 2018-03-07 at 13.36.51.png

Comments (4)

  1. Patrick Fiaux

    We've had this but also unrelated to pull requests, mainly email notifications with the wrong user listed as the author (but with the correct author in the details list of commits).

    I've seen it happen in:

    • Recent activity on the bitbucket project overview (on a branch where there was no PR and the user mentioned as the author did not work on that branch at all)
    • PR update email notifications
    • Pipelines failed email notifications

    Other strange points when this happens: When notifications use the wrong user they always use the same wrong user (one of our team members, say A) So far I've only seen the commits from 2 team members (say B and C) affected with this (they both look like they're from the member A), it does not trigger for other people

    As a result those 2 team members (B and C) get notifications for their on updates to their PRs (normaly not sent) since the email thinks A did the udpate (even though the commits belong to B or C)

  2. Alastair Wilkes staff

    Commits have two pieces of metadata: author and committer. Currently, everywhere (except Pipelines) we always display the commit author even in cases where the committer is someone else. We may add committer info elsewhere in the UI at some point, but this is currently expected behavior.

  3. Log in to comment