-
Notifications
You must be signed in to change notification settings - Fork 189
Remove migrateLegacyFunctions #6111
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
base: 07-14-send_uuid_on_app_version_create_to_do_app_matching
Are you sure you want to change the base?
Remove migrateLegacyFunctions #6111
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
207dc02
to
d650f9e
Compare
d3f1f29
to
5099ba9
Compare
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3044 tests passing in 1314 suites. Report generated by 🧪jest coverage report action from 46089a7 |
d650f9e
to
cde3ba4
Compare
0941461
to
df98fb0
Compare
cde3ba4
to
b5ba43f
Compare
b5ba43f
to
46089a7
Compare
df98fb0
to
7a09ce3
Compare
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
WHY are these changes introduced?
This PR removes the legacy function migration code that is no longer needed.
WHAT is this pull request doing?
Removes the
migrateLegacyFunctions
function and its usage in theautomaticMatchmaking
function. This code was previously used to handle the migration of legacy functions by matching them with their new counterparts, but is no longer necessary.How to test your changes?
Measuring impact
How do we know this change was effective? Please choose one:
Checklist