yp05327 daf2a4c047 Fix wrong display of recently pushed notification (#25812) ... There's a bug in #25715: If user pushed a commit into another repo with same branch name, the no-related repo will display the recently pushed notification incorrectly. It is simple to fix this, we should match the repo id in the sql query.  The latest commit is 2 weeks ago.  The notification comes from another repo with same branch name:  After: In forked repo:  New PR Link will redirect to the original repo:  In the original repo:  New PR Link:  In the same repo:  New PR Link:  08/15 Update: Follow #26257, added permission check and logic fix mentioned in https://github.com/go-gitea/gitea/pull/26257#discussion_r1294085203 2024/04/25 Update: Fix #30611 --------- Co-authored-by: silverwind <me@silverwind.io> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>		2024-05-21 17:00:35 +00:00
..
main_test.go
mini_org.go
org.go	Check the token's owner and repository when registering a runner (#30406)	2024-04-11 16:01:44 +08:00
org_repo.go
org_test.go	Resolve lint for unused parameter and unnecessary type arguments (#30750)	2024-04-29 08:47:56 +00:00
org_user.go
org_user_test.go	Fix wrong display of recently pushed notification (#25812)	2024-05-21 17:00:35 +00:00
team.go	Enable more revive linter rules (#30608)	2024-04-22 11:48:42 +00:00
team_invite.go
team_invite_test.go
team_list.go
team_repo.go
team_test.go
team_unit.go
team_user.go	Add user blocking (#29028)	2024-03-04 08:16:03 +00:00