Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
suntsu42 opened this issue Jan 7, 2025 · 3 comments
Open
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@suntsu42
Copy link

suntsu42 commented 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

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

@lunny lunny added type/proposal The new feature has not been accepted yet but needs to be discussed first. and removed type/bug labels Jan 7, 2025
@lunny
Copy link
Member

lunny commented 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.

@suntsu42
Copy link
Author

suntsu42 commented 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.

@lunny
Copy link
Member

lunny commented 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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants