-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Migration Tweaks #6260
Migration Tweaks #6260
Conversation
Adds error checking before sanitization in migration Signed-off-by: jolheiser <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #6260 +/- ##
=========================================
Coverage ? 41.57%
=========================================
Files ? 446
Lines ? 60848
Branches ? 0
=========================================
Hits ? 25296
Misses ? 32269
Partials ? 3283 Continue to review full report at Codecov.
|
Signed-off-by: jolheiser <[email protected]>
Signed-off-by: jolheiser <[email protected]>
Signed-off-by: jolheiser <[email protected]>
I think this is ready for review. Let me know if you'd prefer an alternate implementation. |
conflicted |
Signed-off-by: jolheiser <[email protected]>
* Adds auto-name if repo name is blank Adds error checking before sanitization in migration Signed-off-by: jolheiser <[email protected]> * Changed err from sanitization to a different variable Signed-off-by: jolheiser <[email protected]> * Remove handleCreatePost and implement separately Signed-off-by: jolheiser <[email protected]> * Make fmt Signed-off-by: jolheiser <[email protected]>
Resolves #6253
Resolves #6254
6253
When migrating, the repo name will attempt to auto-name when the migrate/clone URL is entered. This will only happen if the repo name is empty so that it doesn't overwrite if the user enters something manually first.
6254
Unfortunately, as I described in the issue itself, the sanitization that happens makes the
IsErrxxx
functions calculate incorrectly, so thehandleCreateError
was throwing 500s when it shouldn't have been.I don't particularly like that there is dupe code now, however, so I will likely try to clean that up before readying this PR for review.
Thoughts and suggestions are welcome.