Submitted by Steve Purcell on Sat, 12/15/2007 - 09:18.
I've been thinking about how to make it work with git, but not actually bashed out an implementation.
The tricky part is that in Subversion, it's easy to see which changes are local and which changes are upstream. In git, however, it's practically mandatory to commit new migrations locally before fetching new clashing migrations from an upstream tree, at which point this plugin would be unable to know which of the clashing migrations is to be renumbered.
When using git-svn, one could at least look to see which commits are "local", ie. have no git-svn-id, but that doesn't solve the general case.
I've been thinking about how to make it work with git, but not actually bashed out an implementation.
The tricky part is that in Subversion, it's easy to see which changes are local and which changes are upstream. In git, however, it's practically mandatory to commit new migrations locally before fetching new clashing migrations from an upstream tree, at which point this plugin would be unable to know which of the clashing migrations is to be renumbered.
When using git-svn, one could at least look to see which commits are "local", ie. have no git-svn-id, but that doesn't solve the general case.