Fix 404 after activating secondary email #10547
Merged
Conversation
This file contains 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
lafriks
approved these changes
Feb 29, 2020
GiteaBot
added
the
lgtm/need 1
techknowlogick
approved these changes
Feb 29, 2020
GiteaBot
added
lgtm/done
|
Shall I make a PR against v1.11 also? |
|
@ashimokawa Yes please send backport |
Codeberg-org
pushed a commit
to Codeberg-org/gitea
that referenced
this pull request
Mar 1, 2020
sapk
pushed a commit
that referenced
this pull request
Mar 1, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After confirming a secondary email, users get redirected to a non-existing URL and get a 404, this should fix it.