Always show owner/repo name in compare page dropdowns

[xingxing21]

Fixes: #36677

The fix is a template-only change in templates/repo/diff/compare.tmpl:16-25.

Before, the display names were built with conditional logic:

All four variables defaulted to just the owner name (Examples)
$HeadCompareName was only upgraded to owner/repo format in two narrow cases:
Same org, different repos
A root repo exists with the same owner as the head repo
All other cases (same-repo PRs, cross-org PRs) got owner-only labels
After, all four variables are unconditionally set to owner/repo format using printf "%s/%s":

- {{$BaseCompareName := printf "%s/%s" $.BaseName $.Repository.Name -}}
- {{- $HeadCompareName := printf "%s/%s" $.HeadRepo.OwnerName $.HeadRepo.Name -}}
- {{- $OwnForkCompareName := "" -}}
- {{- if .OwnForkRepo -}}
-	{{- $OwnForkCompareName = printf "%s/%s" .OwnForkRepo.OwnerName .OwnForkRepo.Name -}}
- {{- end -}}
- {{- $RootRepoCompareName := "" -}}
- {{- if .RootRepo -}}
-	{{- $RootRepoCompareName = printf "%s/%s" .RootRepo.OwnerName .RootRepo.Name -}}
- {{- end -}}

+ {{$BaseCompareName := $.Repository.FullName -}}
+ {{$HeadCompareName := $.HeadRepo.FullName -}}
+ {{$OwnForkCompareName := "" -}}
+ {{if $.OwnForkRepo -}}
+	{{$OwnForkCompareName = $.OwnForkRepo.FullName -}}
+ {{end -}}
+ {{$RootRepoCompareName := "" -}}
+ {{if $.RootRepo -}}
+	{{$RootRepoCompareName = $.RootRepo.FullName -}}
+ {{end -}}

These variables drive the labels in the base and head branch selector buttons and their dropdown items. No backend changes were needed — $.BaseName, $.Repository.Name, $.HeadRepo.OwnerName, and $.HeadRepo.Name were already available in the template context.

[Copilot]

Pull request overview

Updates the compare page branch selector labels so they consistently display owner/repo instead of sometimes showing only the owner name.

Changes:

• Build $BaseCompareName and $HeadCompareName unconditionally as owner/repo.
• Build $OwnForkCompareName and $RootRepoCompareName as owner/repo when those repos are present.
• Remove prior conditional logic that only sometimes upgraded head display names.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[silverwind]

Good change imho. Better to show owner all the time. This is consistent with GitHub too, but they have separate dropdown for owner which Gitea currently does not have, so it's fine given the current design.

In the future, we should implement separate dropdown like GitHub.

[bircni]

Could you please adjust the pr description? Its somehow destroyed

[xingxing21]

@bircni I just adjusted the PR description

[xingxing21]

Hi @GiteaBot

I wanted to kindly ask if you might have time to take a look at this PR when convenient. I’d really appreciate any feedback or suggestions you may have.

Thank you for your time and for maintaining the project!

[bircni]

Giteabot is just a bot he won't respond 😊

[xingxing21]

Hello @bircni
I wanted to kindly ask if you might have time to take a look at this PR when convenient. I’d really appreciate any feedback or suggestions you may have.

Thank you for your time and for maintaining the project!

[bircni]

PR description needs to be adjusted after @wxiaoguang s fix

[xingxing21]

@bircni
I just changed the description after @wxiaoguang s fix
Thanks!

And one question:

Merging is blocked
You're not authorized to push to this branch. Visit https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches for more information.

I'm seeing above message on my PR.
How can I authorize to push to this branch?

[bircni]

And one question:

Merging is blocked
You're not authorized to push to this branch. Visit https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches for more information.

I'm seeing above message on my PR. How can I authorize to push to this branch?

Per default mergers and toc can push to your branch, when "allow maintainers to push" is active for your pr
You see this as you are not allowed to merge this to main - thats why there is this "You're not authorized to push to this branch. "

[xingxing21]

@bircni , Thank you for your answer 😉