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
..
api	Fix "force private" logic (#31012)	2024-05-20 00:56:45 +00:00
common	Refactor AppURL usage (#30885)	2024-05-07 08:26:13 +00:00
install	Always load or generate oauth2 jwt secret (#30942)	2024-05-14 14:21:38 +00:00
private	Move database operations of merging a pull request to post receive hook and add a transaction (#30805)	2024-05-07 07:36:48 +00:00
utils	Refactor external URL detection (#29973)	2024-03-22 04:32:40 +08:00
web	Fix wrong display of recently pushed notification (#25812)	2024-05-21 17:00:35 +00:00
init.go	Make sure git version&feature are always prepared (#30877)	2024-05-06 18:34:16 +02:00