-
Notifications
You must be signed in to change notification settings - Fork 518
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
Backport 20230824 #20207
Backport 20230824 #20207
Conversation
A new version of the staging env has been deployed 🎉 |
c6dc02d
to
ac5be55
Compare
A new version of the staging env has been deployed 🎉 |
23bb80f
to
7de42d7
Compare
A new version of the staging env has been deployed 🎉 |
7de42d7
to
b6c97de
Compare
A new version of the staging env has been deployed 🎉 |
2 similar comments
A new version of the staging env has been deployed 🎉 |
A new version of the staging env has been deployed 🎉 |
b6c97de
to
6a065fb
Compare
A new version of the staging env has been deployed 🎉 |
6a065fb
to
72a9f45
Compare
A new version of the staging env has been deployed 🎉 |
72a9f45
to
04521bf
Compare
A new version of the staging env has been deployed 🎉 |
A new version of the staging env has been deployed 🎉 |
Description (for Contributor and Core Developer)
The most important part of the PR is the script: backport.sh.
Doing like we do for pull up cannot be done between repositories, we cannot "merge".
Instead, what is does is the following:
last_backport.txt
.last_backport.txt
so the next backport can start from where we stopped.bundles.php
automatically, new bundles need to be added manually).upgrades/
directories were merged together, EE migrations are backported by default, I removed them in a follow-up commit.Definition Of Done (for Core Developer only)