[eloff]

I used to lose so much time to that, imagine coupling it with multi week code reviews (another process that needed to be fixed). I'm actually building a migration tool as part of a web framework (free time project). I'm going to "steal" this idea of yours if you don't mind.

To play devil's advocate, probably part of the reason for the sequence number approach is so if that PR that merged ahead of you conflicts with your migration you're more likely to notice if you have to rename it. I don't think that's particularly common though, and the problem should surface when the CI build runs your migrations prior to permitting the merge to master ( a good CI setup requires you to pull master into your PR if it's out of date, which ensures the combination didn't break things.)