-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Refactor repository transfer #33211
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
Merged
Refactor repository transfer #33211
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
5acc289
refactor transfer related code
lunny 237a09c
Fix bugs
lunny 94caa39
Fix test
lunny 07d1a37
Fix bugs
lunny 45ffedd
Fix bug
lunny 2f1fc75
Some improvements
lunny 877b676
Merge branch 'main' into lunny/refactor_transfer
lunny 6bd16bd
Follow reviews
lunny f286ace
Merge branch 'main' into lunny/refactor_transfer
lunny 78b1cb9
Some improvements
lunny 7edb840
Fix the permission check
lunny 9e53ad7
Merge branch 'main' into lunny/refactor_transfer
lunny cb24f72
Follow @wxiaoguang's suggestion
lunny 58d6d50
Merge branch 'main' into lunny/refactor_transfer
lunny 0a51b67
Update repo.go
wxiaoguang 515ee5f
Update repo.go
wxiaoguang b80f349
Update services/repository/transfer.go
wxiaoguang 01ebb16
Merge branch 'main' into lunny/refactor_transfer
GiteaBot a7d4f35
Merge branch 'main' into lunny/refactor_transfer
GiteaBot 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
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.
It seems that this is unnecessary. If you got a User pointer, it should come from a
GetUserByxxx
function, so the user exist check is already done before calling this function, and even ifnewOwner
is nil (although it is impossible), this will cause panic.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.
Because this test introduced a non-exist user. So we need to check it here.
