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
Over the years we have several 100 migration scripts which will probably never be run again but which we'd like to keep for reference. Is there a best practice for dealing with older scripts? For example is it as simple as just pushing these to an archive folder?
The text was updated successfully, but these errors were encountered:
I work on a single deployment product, so I feel fine deleting the migration files and the migration records, and then rely on version control if I ever want to go back to them.
Cheers Dave. Just wanted to see if there was a "best practice" way of dealing with this. Deleting them is probably best as less files for the script to try and work it's way through. Like you said they can always be pulled from version control if needed.
Over the years we have several 100 migration scripts which will probably never be run again but which we'd like to keep for reference. Is there a best practice for dealing with older scripts? For example is it as simple as just pushing these to an archive folder?
The text was updated successfully, but these errors were encountered: