You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user who pushed a change must not be the same user who did the commit.
The user who is listed in the commit is not even required to exist on the gitea server.
On the start page of gitea, it shows which user pushed the latest commits together with the commit user.
I did not find the same information in the repository/commit overview. There, only the commit user can be found, but no information about which user did push the commit.
Is it possible to get the Push User to a certain commit either via website or via rest api?
Gitea Version
1.22.6
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Run official gitea on a windows server
Database
None
The text was updated successfully, but these errors were encountered:
I don't think it's possible at the moment. The pusher's user id will be saved to a feed table (named action). But the table should not be search by repository id and commit id.
Description
The user who pushed a change must not be the same user who did the commit.
The user who is listed in the commit is not even required to exist on the gitea server.
On the start page of gitea, it shows which user pushed the latest commits together with the commit user.
I did not find the same information in the repository/commit overview. There, only the commit user can be found, but no information about which user did push the commit.
Is it possible to get the Push User to a certain commit either via website or via rest api?
Gitea Version
1.22.6
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Run official gitea on a windows server
Database
None
The text was updated successfully, but these errors were encountered: