-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Fix commits pushed with deploy keys not shown in dashboard #24521
Conversation
Haven't tested, I have a question: Is the new SQL friendly to |
Yes, the |
* upstream/main: Remove unnecessary code (go-gitea#24610) Fix commits pushed with deploy keys not shown in dashboard (go-gitea#24521) fix: release page for empty or non-existing target (go-gitea#24470) Filter get single commit (go-gitea#24613) Attach a tooltip to the action status icon (go-gitea#24614) Use official Vue extension in Gitpod (go-gitea#24609) Create a branch directly from commit on the create branch API (go-gitea#22956) Make repository response support HTTP range request (go-gitea#24592)
Fix #21324
In the current logic, if the
Actor
user is not an admin user, all activities from private organizations won't be shown even if theActor
user is a member of the organization.As mentioned in the issue, when using deploy key to make a commit and push, the activity's
act_user_id
will be the id of the organization so the activity won't be shown to non-admin users because the visibility of the organization is private.gitea/models/activities/action.go
Lines 490 to 503 in 55a5717
This PR improves this logic so the activities of private organizations can be shown.