Skip to content
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

Fix has_migrations? check in Rails::Engine #1945

Merged
merged 1 commit into from
Jul 3, 2011

Conversation

spohlenz
Copy link
Contributor

@spohlenz spohlenz commented Jul 3, 2011

Currently the install:migrations rake task for an engine is added even if no migrations directory exists, due to a broken check in the has_migrations? method.

josevalim added a commit that referenced this pull request Jul 3, 2011
Fix has_migrations? check in Rails::Engine
@josevalim josevalim merged commit a1d85a0 into rails:master Jul 3, 2011
@josevalim
Copy link
Contributor

If this is broken in 3-1-stable, could you please submit a patch as well? :) Thanks!

@spohlenz
Copy link
Contributor Author

spohlenz commented Jul 3, 2011

The check is also broken in 3-1-stable.

However can you clarify the process required? I'm guessing I create a new branch off of 3-1-stable, cherry pick the commit and create a new pull request?

@spohlenz
Copy link
Contributor Author

spohlenz commented Jul 3, 2011

Similarly, what is the current policy on commits to master making it into 3-1-stable?
Is it possible for my other recent patch (3875e44) to make it in?

@josevalim
Copy link
Contributor

Yeah, create a new branch of 3-1-stable, cherry-pick both commits and send a new pull request with copy to me pls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants