-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
feat(api): support ref suffixes in compare #38148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
eyupcanakman
wants to merge
11
commits into
go-gitea:main
Choose a base branch
from
eyupcanakman:feat/compare-ref-suffix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
0efa2be
feat(api): support ref suffixes in compare
eyupcanakman 05ddcec
fix(api): return 400 for unsupported ref suffixes in compare
eyupcanakman d09be15
feat(web): support ref suffixes in the compare page
eyupcanakman 6f3e238
refactor(compare): return errors from ResolveRefWithSuffix
eyupcanakman 64f3536
Merge branch 'main' into feat/compare-ref-suffix
GiteaBot 43c7892
Merge branch 'main' into feat/compare-ref-suffix
GiteaBot 4b96a47
Merge branch 'main' into feat/compare-ref-suffix
GiteaBot 71eab7b
Merge branch 'main' into feat/compare-ref-suffix
GiteaBot 68ce8e0
minor nits
bircni f488fc0
Merge remote-tracking branch 'origin/main' into feat/compare-ref-suffix
bircni 65af672
fix
bircni File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a suffix is present this bypasses
UnstableGuessRefByShortNameand asks git to resolve the raw short name plus suffix. In repositories where a branch and tag share the same name, the non-suffixed compare path resolves the branch first, butcompare/v1^...mainfeedsv1^to git and git reports the ambiguous ref as missing, so users cannot compare the branch parent. ResolveoriRefto the branch/tag/SHA first and append the suffix to that full ref to preserve the existing branch-first semantics.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a related edge case worth mentioning. When a branch and tag share a name, the suffix path uses the default git order instead of checking branches first (
UnstableGuessRefByShortName), soname^can pick the tag. I can fix it here, or open a follow-up if you want to keep this PR focused.