Avoid losing token when updating mirror settings (#30429) #30464
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.
Backport #30429 by @wolfogre
Fix #30416.
Before (it shows as "Unset" while there's a token):
After:
The username shows as "oauth2" because of
gitea/services/migrations/dump.go
Line 99 in f9fdac9
I have checked that all usage of
MirrorRemoteAddress
has been updated.However, it needs to be checked again when backporting.