I have a git repository that contains the database migrations scripts history. Those files become immutable as soon as they are executed. (We use Flyway to apply migrations, which are frequent).
The good benefit from using git in this purpose, is to allow code reviews between coders, before altering the database state.
However, I am not comfortable with having history code versioned on git as the files won't change after.
example:
commit 1: migration_1.sql
commit 2: migration_1.sql migration_2.sql
commit 3: migration_1.sql migration_2.sql migration_3.sql
commit n: migration_1.sql ... ... migration_n.sql
My need is to have the ability to review code on git, but only store it on a filesystem without versioning it.
I think of git LFS (large file system) ! Does it do the job? is there some pitfalls to be aware of ?
Or, is there another ways to manage migrations and code reviews ?