Email notification for build failure is not showing the correct commit author

Summary

Pipelines email notification description is showing the name of the user who triggered the build, but not the actual author of the commit
Based on our observation from the following email notification format, the <Name> field should disable the Commit author's name:

<WorkspaceID> / <Repo-Name>

<Build Status>	<Duration>
<Branch Name>
<Name> committed <commit-hash>
<commit message>

However, the current email notification is displaying the actor who triggered the build instead.

Sample image

1. Commit Author(Grey Color)
   
2. After we run the multiple builds with a different account on the same commit, the Email Notifications showing two different users committed "3b49707"
   

 Steps to Reproduce

Please do ensure that the accounts had watched the repository in order to get an email notification

• Add the following configuration to bitbucket-pipelines.yml to simulate a fail build

  pipelines:
    default:
      - step:
          script:
            - exit 1
  

• Create a commit then navigate to the commit's page
• Click "Run pipelines" to trigger the fail build
• Login to a different account and access the same commit page
• Click on "Run Pipelines" again to trigger builds
• Check the email inbox

Expected Results

The <Name> mentioned in email notification should remain as the "Commit Author", and not the actor who triggers the Pipelines build

<Commit Author(Grey)> committed 3b49707
test edited online with Bitbucket

Actual Results

The <Name> mentioned in email notification displays the actor who triggers the Pipelines build

<Pipelines Actor> committed 3b49707
test edited online with Bitbucket

Notes

If the email notification should show the Actor who triggers the build, the content of the email should update as following:

<Pipelines Actor> runs build on the commit 3b49707
test edited online with Bitbucket

Initial Description

When I merge a PR and a pipelines fails, the email that is sent says I committed the failing commit.
Which is not true, but I did add it to the repo.