Hi, nice gem! The only thing we constantly run into is merge conflicts of branches when 2 people added new database migrations. At the bottom of the structure.sql there will be different versions which end with a semicolon.
The versions are currently listed as follows:
INSERT INTO "schema_migrations" (version) VALUES
('20190503120501'),
('20190506124902'),
('20190508123941'),
('20190508132644');
I think we can prevent a lot of merge conflicts if we uglify this a bit:
INSERT INTO "schema_migrations" (version) VALUES
('20190503120501')
,('20190506124902')
,('20190508123941')
,('20190508132644')
;
Let me know what you think. I can create a PR for this if you like.
Hi, nice gem! The only thing we constantly run into is merge conflicts of branches when 2 people added new database migrations. At the bottom of the structure.sql there will be different versions which end with a semicolon.
The versions are currently listed as follows:
I think we can prevent a lot of merge conflicts if we uglify this a bit:
Let me know what you think. I can create a PR for this if you like.