forgejo/templates/repo/code/recently_pushed_new_branche...

{{range .RecentlyPushedNewBranches}}
	<div class="ui positive message tw-flex tw-items-center">
		<div class="tw-flex-1">
			{{$timeSince := TimeSince .CommitTime.AsTime ctx.Locale}}
			{{$repo := .GetRepo $.Context}}
			{{$name := .Name}}
			{{if ne $repo.ID $.Repository.ID}}
				{{$name = (print $repo.FullName ":" .Name)}}
			{{end}}
			{{$branchLink := (print ($repo.Link) "/src/branch/" (PathEscapeSegments .Name))}}
			{{ctx.Locale.Tr "repo.pulls.recently_pushed_new_branches" $name $timeSince $branchLink}}
		</div>
		<a role="button" class="ui compact positive button gt-m-0" href="{{$.Repository.ComposeBranchCompareURL $.Repository.BaseRepo $name}}">
			{{ctx.Locale.Tr "repo.pulls.compare_changes"}}
		</a>
	</div>
{{end}}
Newly pushed branches hints on repository home page (#25715) This PR will display a pull request creation hint on the repository home page when there are newly created branches with no pull request. Only the recent 6 hours and 2 updated branches will be displayed. Inspired by #14003 Replace #14003 Resolves #311 Resolves #13196 Resolves #23743 co-authored by @kolaente 2023-07-08 05:19:00 +02:00			`{{range .RecentlyPushedNewBranches}}`
Fix incorrect tailwind migration (#30007) Fixes https://github.com/go-gitea/gitea/issues/30005. Regression from https://github.com/go-gitea/gitea/pull/29945. There was only once instance of `tw-content-center` before that PR, so I just ran below command and reverted that one instance. ```sh perl -p -i -e 's#tw-content-center#tw-items-center#g' web_src/js/*/ templates/*/ models/*/ tests/*/ ``` (cherry picked from commit 04f9ad056882fc3f21b247b16f84437adf0f36d8) Conflicts: templates/repo/diff/conversation.tmpl templates/repo/header.tmpl templates/repo/issue/filter_list.tmpl templates/repo/issue/view_content/conversation.tmpl templates/repo/wiki/view.tmpl web_src/js/components/DashboardRepoList.vue re-ran the command after discarding the Gitea changes to ensure all Forgejo files are also covered 2024-03-22 20:51:29 +01:00			`<div class="ui positive message tw-flex tw-items-center">`
Replace 10 more gt- classes with tw- (#29945) Likely the biggest change of the tailwind refactors. Only thing of note is that `tw-flex-1` resolves to `flex: 1 1 0%` while our `gt-f1` was `flex: 1 1 0`, I don't think it will make any difference. Commands I've ran: ```sh perl -p -i -e 's#gt-vm#tw-align-middle#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-fw#tw-flex-wrap#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-f1#tw-flex-1#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-fc#tw-flex-col#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-sb#tw-justify-between#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-je#tw-justify-end#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-jc#tw-justify-center#g' web_src/js/*/ templates/*/ models/*/ perl -p -i -e 's#gt-ac#tw-content-center#g' web_src/js/*/ templates/*/ models/*/ tests/*/ perl -p -i -e 's#gt-df#tw-flex#g' web_src/js/*/ templates/*/ models/*/ tests/*/ perl -p -i -e 's#gt-dib#tw-inline-block#g' web_src/js/*/ templates/*/ models/*/ tests/*/ Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> (cherry picked from commit f88ad5424f381bf2a45fd863b551c5a72891bb68) Conflicts: templates/repo/diff/conversation.tmpl templates/repo/header.tmpl templates/repo/issue/filter_actions.tmpl templates/repo/issue/filter_list.tmpl templates/repo/issue/view_content/conversation.tmpl templates/repo/release/list.tmpl templates/repo/wiki/view.tmpl web_src/js/components/DashboardRepoList.vue discard the proposed changes and prefer Forgejo. A followup commit will apply the same commands. 2024-03-22 14:45:10 +01:00			`<div class="tw-flex-1">`
Fix more "locale" usages (#27259) 2023-09-25 14:42:40 +02:00			`{{$timeSince := TimeSince .CommitTime.AsTime ctx.Locale}}`
[GITEA] Rework when recently pushed branches are displayed With this change, the "You pushed on branch xyz" banner will be displayed when either the viewed repository or its base repo (if the current one's a fork) has pull requests enabled. Previously it only displayed if the viewed repo had PRs enabled. Furthermore, if the viewed repository is an original repository that the viewing user has a fork of, if the forked repository has recently pushed branches, then the banner will appear for the original repository too. In this case, the notification will include branches from the viewing user's fork, and branches they pushed to the base repo, too. Refs: https://codeberg.org/forgejo/forgejo/pulls/2195 Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu> (cherry picked from commit a29f10661d59f6c33c5cfbee723f03f981aa6b72) (cherry picked from commit 70c5e2021d7c385b9285622f0b2d878d3807d33c) (cherry picked from commit 48b25be67a94f739601fbfea951ade6cdfe30691) 2024-01-21 15:18:24 +01:00			`{{$repo := .GetRepo $.Context}}`
			`{{$name := .Name}}`
			`{{if ne $repo.ID $.Repository.ID}}`
			`{{$name = (print $repo.FullName ":" .Name)}}`
			`{{end}}`
			`{{$branchLink := (print ($repo.Link) "/src/branch/" (PathEscapeSegments .Name))}}`
Remove incorrect and unnecessary Escape from templates (#29394) Follow #29165 * some of them are incorrect, which would lead to double escaping (eg: `(print (Escape $.RepoLink)`) * other of them are not necessary, because `Tr` handles strings&HTML automatically Suggest to review by "unified view": https://github.com/go-gitea/gitea/pull/29394/files?diff=unified&w=0 (cherry picked from commit d2f6588b66549b33adf8bac7044d03c89d668470) Conflicts: templates/code/searchcombo.tmpl templates/mail/auth/register_notify.tmpl templates/mail/issue/default.tmpl templates/repo/code/recently_pushed_new_branches.tmpl templates/repo/search.tmpl templates/repo/settings/protected_branch.tmpl templates/user/auth/activate.tmpl templates/user/auth/forgot_passwd.tmpl templates/user/dashboard/feeds.tmpl context 2024-02-25 15:02:20 +01:00			`{{ctx.Locale.Tr "repo.pulls.recently_pushed_new_branches" $name $timeSince $branchLink}}`
Newly pushed branches hints on repository home page (#25715) This PR will display a pull request creation hint on the repository home page when there are newly created branches with no pull request. Only the recent 6 hours and 2 updated branches will be displayed. Inspired by #14003 Replace #14003 Resolves #311 Resolves #13196 Resolves #23743 co-authored by @kolaente 2023-07-08 05:19:00 +02:00			`</div>`
[GITEA] Rework when recently pushed branches are displayed With this change, the "You pushed on branch xyz" banner will be displayed when either the viewed repository or its base repo (if the current one's a fork) has pull requests enabled. Previously it only displayed if the viewed repo had PRs enabled. Furthermore, if the viewed repository is an original repository that the viewing user has a fork of, if the forked repository has recently pushed branches, then the banner will appear for the original repository too. In this case, the notification will include branches from the viewing user's fork, and branches they pushed to the base repo, too. Refs: https://codeberg.org/forgejo/forgejo/pulls/2195 Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu> (cherry picked from commit a29f10661d59f6c33c5cfbee723f03f981aa6b72) (cherry picked from commit 70c5e2021d7c385b9285622f0b2d878d3807d33c) (cherry picked from commit 48b25be67a94f739601fbfea951ade6cdfe30691) 2024-01-21 15:18:24 +01:00			`<a role="button" class="ui compact positive button gt-m-0" href="{{$.Repository.ComposeBranchCompareURL $.Repository.BaseRepo $name}}">`
Always use `ctx.Locale.Tr` inside templates (#27231) 2023-09-25 10:56:50 +02:00			`{{ctx.Locale.Tr "repo.pulls.compare_changes"}}`
Newly pushed branches hints on repository home page (#25715) This PR will display a pull request creation hint on the repository home page when there are newly created branches with no pull request. Only the recent 6 hours and 2 updated branches will be displayed. Inspired by #14003 Replace #14003 Resolves #311 Resolves #13196 Resolves #23743 co-authored by @kolaente 2023-07-08 05:19:00 +02:00			`</a>`
			`</div>`
			`{{end}}`