Date: Fri, 29 Mar 2024 14:42:50 +0000 (UTC) Message-ID: <1825755233.9.1711723370351@dab67b52ff4f> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8_852644827.1711723370351" ------=_Part_8_852644827.1711723370351 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This article describes how to handle what to do when you wish to= revert a migration that has already made it to master.
It is important to understand that a migration that has made it to maste= r could already have been run in many environments, including developer dev= stacks. Although Production may be the first concern, you must follow= -up with help for all other environments.
Here's what you do to resolve removing a bad migration from master.
A sample email might look like the following:
The following migration was reverted from master during the last release= (005_blahblah).
If you run into the following error on your devstack:
(1054, "Unknown column 'commerce_commerceconfiguration.receipt_page' in = 'field list'")
You can fix it with the following:
You may also need to run the following sql manually:
mysql -u root edxapp
ALTER TABLE ...;
If you know the error that developers are facing, include that in the Sl= ack messages so it can be easily found.