Issue Summary

Merging two pull requests within an extremely short interval can cause the pull-request UI to display the user who merged the first PR as the merger of the following PR.

Repository commit history and merge records show that the correct users performed the respective merges. The issue is limited to the merger attribution displayed in the pull-request UI and does not change the underlying Git history.

Steps to Reproduce

1. Have two pull requests ready to merge into the same destination branch.
2. Merge the first pull request.
3. Merge the second pull request within a few seconds of the first merge.
4. Review the merger attribution shown in the second pull request.
   Very inconsistent to reproduce, and sometimes it worked fine.

Expected Results

The second pull request displays the user who performed the merge as the merger.

Actual Results

The second pull request can display the user who merged the first pull request as its merger.

The issue appears to occur within an extremely small timing window and is difficult to reproduce consistently.

Workaround

Avoid merging multiple pull requests within only a few seconds of each other where practical. Before merging, check the target branch’s recent activity to confirm whether another PR has just been merged.

If Merge Queue is available in the workspace, it may also be used to serialize merges as a temporary mitigation.

For already affected PRs, use the merge commit and repository commit history as the source of truth for the actual merge.