-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrations differ in db/migrate to spec/dummy/db/migrate #141
Comments
My guess is because spec/dummy/db/migrate shouldn't be in the repo in the first place. I have other engines where I've pushed them up, and it's always been a mistake then. |
Agree, I think we should refactor it out and make it a task instead. |
Please Do Investigate |
Oh no he didn't |
Please see #149. |
This is fixed in #149. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@knewter @radar do you know why?
The text was updated successfully, but these errors were encountered: