You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we store only the migration script file name as an entry after the migration is run. I think it will be a good idea to store the description of what changed with the script so that when one reads the entry, they can see what applied without going to the code.
This can be the same description of what was applied when the migration is deployed.
The text was updated successfully, but these errors were encountered:
I will come back to you later with an answer so that it will be clear on what the descriptions for each possible actions will be, and how we can likely get those descriptions.
Currently, we store only the migration script file name as an entry after the migration is run. I think it will be a good idea to store the description of what changed with the script so that when one reads the entry, they can see what applied without going to the code.
This can be the same description of what was applied when the migration is deployed.
The text was updated successfully, but these errors were encountered: