[Proposal] Add rake task to update timestamp of an existing migration file

Hello! I would like to propose a feature rake task to update the timestamp of an existing migration file since in some cases rebased feature branches may have out of sync migration files. Generally, what I tend to do in those cases is to delete my migration file in my feature branch and generate a new one so that it has the most current timestamp and doesn’t conflict with my main branch migrations… But wanted to see what other people thought about it, and if we could add this sort of feature.

I’m actually not following why you change the timestamp in the first place? What harm comes with leaving the old timestamp?