mirror of
https://github.com/go-gitea/gitea
synced 2024-11-09 11:44:27 +00:00
daf2a4c047
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>
13 lines
525 B
Handlebars
13 lines
525 B
Handlebars
{{range .RecentlyPushedNewBranches}}
|
|
<div class="ui positive message tw-flex tw-items-center">
|
|
<div class="tw-flex-1">
|
|
{{$timeSince := TimeSince .CommitTime.AsTime ctx.Locale}}
|
|
{{$branchLink := HTMLFormat `<a href="%s">%s</a>` .BranchLink .BranchDisplayName}}
|
|
{{ctx.Locale.Tr "repo.pulls.recently_pushed_new_branches" $branchLink $timeSince}}
|
|
</div>
|
|
<a role="button" class="ui compact green button tw-m-0" href="{{.BranchCompareURL}}">
|
|
{{ctx.Locale.Tr "repo.pulls.compare_changes"}}
|
|
</a>
|
|
</div>
|
|
{{end}}
|