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 master could already have been run in many environments, including developer devstacks. 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:
|
If you know the error that developers are facing, include that in the HipChat/Slack messages so it can be easily found.
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|