-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Validate that the tag doesn't exist when creating a tag via the web #33241
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
Merged
wxiaoguang
merged 17 commits into
go-gitea:main
from
kemzeb:fix/ui/release-post-with-tag-only
Jan 14, 2025
Merged
Changes from 12 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
62d47e0
Validate that the tag doesn't exist when creating a tag via the web
kemzeb 69984e5
PR feedback
kemzeb a3a6493
Fix typo in test
kemzeb 7a5595c
add comments for the "string" type
wxiaoguang 10c6287
Merge branch 'main' into fix/ui/release-post-with-tag-only
wxiaoguang 5cf8947
fix legacy bugs
wxiaoguang 7d77978
fix legacy bugs
wxiaoguang d190fb6
add comments
wxiaoguang 982cb1f
fix test
wxiaoguang 3ca836c
rewrite tests
wxiaoguang 1f8952f
fix test
wxiaoguang f68bee5
add more tests
wxiaoguang 57aef6d
fix tag-only button logic
wxiaoguang be79b34
add more comments
wxiaoguang 43c5100
improve comment
wxiaoguang 7cd7d60
improve test
wxiaoguang 6633188
Merge branch 'main' into fix/ui/release-post-with-tag-only
wxiaoguang 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
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.
Big fan of the test refactor. Everything looks good to me, the only problem that I see now is the "Create Tag Only" problem we discussed earlier:
To reproduce:
It looks like this happens because the "error form" page we return now has a
tag_name
that points to an existingRelease
, which would set the highlighted line totrue
.Would it make sense to set this to something like:
Uh oh!
There was an error while loading. Please reload this page.
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.
Hmm, I think the problem is: we shouldn't stop users from creating new "tag-only" if the error occurs, no matter whether the release exists.
So I think this line should be completely removed.Uh oh!
There was an error while loading. Please reload this page.
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.
Made some changes in 57aef6d
Does it sound right?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yes it sounds about right
Hmm it looks like the only case where we do hide it is when a
tag_name
field is passed which refers to an existing tag (I guess we hide it to avoid any confusion by users). I think it is fine to follow your alternative approach and have the button always appear since the user would be shown an error in case they do press it, but it's up to you