Merge v1.21 into v2.3 - #1962
Conversation
Enable 2 new features when creating merge-up PR: - Add "merge-up" label - Assign the approver of the merged pull request Backport rector fixes and drivers-evergreen-tools update in order to make the CI pass
|
There is an existing patch(es) for this commit SHA: Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'. |
❌ 38 Tests Failed:
View the full list of 41 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
a9773ca to
ac3ae69
Compare
# Conflicts: # .github/workflows/merge-up.yml # rector.php # tests/Model/IndexInfoFunctionalTest.php
ac3ae69 to
29ce890
Compare
Merge new changes from v1.21 into v2.3.
Commits
To resolve any conflicts, check out the temporary branch and run the following command:Resolving conflicts
To ignore from the remote branch, first reset the temporary branch to v2.3 and manually merge using the `ours` merge strategy:Ignoring changes
Then, push the temporary branch to update the pull request.