Is there a way via website or rest api to get the push user to a commit #13922

New Issue

GiteaMirror · 2025-11-02T10:57:21-06:00

GiteaMirror commented

2025-11-02 10:57:21 -06:00

Originally created by @suntsu42 on GitHub (Jan 7, 2025).

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

Originally created by @suntsu42 on GitHub (Jan 7, 2025). ### 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. ![image](https://github.com/user-attachments/assets/6a974f16-b977-4b11-bff4-f8b227155aa2) 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

GiteaMirror added the type/proposal label 2025-11-02 10:57:21 -06:00

GiteaMirror commented

2025-11-02 10:57:22 -06:00

@lunny commented on GitHub (Jan 7, 2025):

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.

@lunny commented on GitHub (Jan 7, 2025): 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.

GiteaMirror commented

2025-11-02 10:57:23 -06:00

@suntsu42 commented on GitHub (Jan 8, 2025):

Thanks for the tip.
This is ok for me. I just needed a way to analyze it for a single commit, and doing it via sql is fine.

@suntsu42 commented on GitHub (Jan 8, 2025): Thanks for the tip. This is ok for me. I just needed a way to analyze it for a single commit, and doing it via sql is fine.

GiteaMirror commented

2025-11-02 10:57:23 -06:00

@lunny commented on GitHub (Jan 8, 2025):

Thanks for the tip. This is ok for me. I just needed a way to analyze it for a single commit, and doing it via SQL is fine.

It's very slow to query in this table. Maybe you can copy to other place and do some indexes before doing analysis.

@lunny commented on GitHub (Jan 8, 2025): > Thanks for the tip. This is ok for me. I just needed a way to analyze it for a single commit, and doing it via SQL is fine. It's very slow to query in this table. Maybe you can copy to other place and do some indexes before doing analysis.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13922