https://github.com/purcell/renumber_migrations

Rails plugin for renumbering clashing migrations in a project kept in svn
https://github.com/purcell/renumber_migrations

Last synced: 3 months ago
JSON representation

Rails plugin for renumbering clashing migrations in a project kept in svn

• Host: GitHub
• URL: https://github.com/purcell/renumber_migrations
• Owner: purcell
• License: mit
• Created: 2008-05-05T08:09:04.000Z (over 16 years ago)
• Default Branch: master
• Last Pushed: 2008-05-05T08:09:50.000Z (over 16 years ago)
• Last Synced: 2023-04-11T05:03:11.222Z (almost 2 years ago)
• Language: Ruby
• Homepage: http://www.sanityinc.com/articles/renumber-rails-migrations
• Size: 78.1 KB
• Stars: 2
• Watchers: 4
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README
  • License: MIT-LICENSE

Awesome Lists containing this project

README

        
RenumberMigrations

==================

Automatically renumber new local migrations when their numbers clash with

team-mates' migrations updated from a subversion repository.

The plugin provides a rake task that has been used without problems for over

a year on a huge project with 8+ developers and over 600 migrations.

The plugin's home on the web is here:

   http://www.sanityinc.com/                                      - articles and news

   http://git.sanityinc.com/?p=renumber_migrations.git;a=summary  - code and downloads

Send feedback or patches by email to [email protected]

Examples

========

You're working on migration 045_add_my_new_feature.rb, when one of your team-mates checks

045_some_other_migration.rb into svn.  You notice the numbering clash (or 'rake db:migrate'

notices it for you), and you simply run the db:migrate:renumber task:

% rake db:migrate:renumber

Voilá - your migration is renumbered to 046, and the database schema is left at version

044 ready for you to re-test your migration.

Requirements

============

Note that renumbering a migration *requires* that you have a working #down method for

your migration.

Renumbering also requires that you have network access to the subversion server, since

clashing migrations are temporarily removed locally, and later re-requested.

Copyright (c) 2007 Steve Purcell, released under the MIT license