github-monolith-migrations

To coordinate database migrations, update configuration files such as db/migrate, db/tableowners.yaml, and db/schema-domains.yml to maintain schema consistency across Rails apps. This ensures changes remain documented and auditable across multiple clusters.

When adding a new table, update db/migrate, db/tableowners.yaml, lib/github/database_structure.rb, db/schema-domains.yml, and sorbet RBI files. These files maintain table ownership, structure, and schema domain consistency across the monolith.

Testing database migrations involves applying specific testing practices and enforcing RuboCop rules to maintain code quality. This ensures schema changes are reliable and meet consistency standards before being applied across clusters.

Update schema domains and table ownership configuration when creating new tables, adding columns, modifying indexes, or updating related configurations. This maintains consistency across defined ownership and domain constraints in the monolith.

Yes, this approach integrates with Sorbet by requiring updates to sorbet/rbi/dsl/*.rbi files. This ensures type definitions remain consistent with database structure changes during the migration process across the monolith.

Managing schema through db/schema-domains.yml requires strict coordination across teams to avoid conflicts. Changes must align with table ownership and domain constraints, and missing updates can cause inconsistencies across multiple clusters.