-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Unify migration descriptions #16781
Unify migration descriptions #16781
Conversation
Codecov Report
@@ Coverage Diff @@
## main #16781 +/- ##
=======================================
Coverage 45.48% 45.49%
=======================================
Files 762 762
Lines 85975 85969 -6
=======================================
+ Hits 39106 39111 +5
+ Misses 40555 40548 -7
+ Partials 6314 6310 -4
Continue to review full report at Codecov.
|
Co-authored-by: Norwin <noerw@users.noreply.github.com>
d115d5b
to
a5d10fb
Compare
This question hasn't been answered yet. |
Hm, for me. Both OK. |
I vote for 1. |
All migration descriptions now follow a unified naming approach.
Additionally, a Gitea migration now no longer asks whether to migrate
Merge requests
, butPull Requests
instead.Fixes #16777.
Fixes #16782.
EDIT: I have just noticed that
Migrate data from <Provider.URL> or another <Provider> instance.
can be used as well instead ofMigrate data from <Provider.URL> or other <Provider> instances.
Which one is preferred?
New appearance
Previous appearance