Default records in the database, fixtures or migrations?

Question

Database migration

There are several development vehicles and one combat vehicle. You need to add an entry to one of the tables for all machines. What is the best way to implement this from aesthetic standards?
Migrations - in theory, are needed only for creating and editing table structures
Fixtures - for filling tables with temporary data before testing. After testing, they should be removed.

Answer 1

We have done the following: there is a dev base on the dev server from which the developers' local machines regularly pull full dumps. Accordingly, it is enough to make changes to this database.
If content changes affect both production and devs, we do it by migration.
If these are local changes only for the dev - to be honest, I don’t remember that we would have such a thing at least once), but you can also use handles directly in the dev base.
But we have a point that greatly simplifies everything - the dev base, in turn, is regularly overwritten with data from production.