Describe the bug
It seems that the bot is not using the commit's author for SSH commits, but is instead using the author of the deploy key.
To Reproduce
Steps to reproduce the behavior:
Set up your GitHub repository as an SSH only repository.
Make a deploy key. (Make sure this is NOT made by the same GitHub user you are going be committing with -- for testing purposes.)
Commit and push to this repository using the SSH deploy key you made prior.
Once the Slack Discord bot sends the message to your channel, it will have the author of the deploy key instead of the author of the commit as the stated author of the git commit.
Expected behavior
The author of the git commit as shown in slack to be the same as shown in GitHub (and more specifically the actual one who committed the commit).
Screenshots
In the image above, the second commit is shown to be using the new deploy key (made by me). The first commit was using a deploy made by danv-vandata.
Desktop (please complete the following information):
OS: doesn't matter
Browser doesn't matter
Version doesn't matter
Smartphone (please complete the following information):
Device: doesn't matter
OS: doesn't matter
Browser doesn't matter
Version doesn't matter
Additional context
Not really anything else that I haven't already said.
Describe the bug It seems that the bot is not using the commit's author for SSH commits, but is instead using the author of the deploy key.
To Reproduce Steps to reproduce the behavior:
Expected behavior The author of the git commit as shown in slack to be the same as shown in GitHub (and more specifically the actual one who committed the commit).
Screenshots In the image above, the second commit is shown to be using the new deploy key (made by me). The first commit was using a deploy made by danv-vandata.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Not really anything else that I haven't already said.