-
Notifications
You must be signed in to change notification settings - Fork 34
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
Generator is broken #3
Comments
Grrr. I merged my previous changes before creating this branch, so it includes some other work (trivial typo fixes and ability to specify an alternative editor in a .bloggyrc file); sorry about that. @whatasunnyday if you are able to test this out, that'd be awesome, it's not a feature I'm planning to use. |
Sure, I'll give it a look sometime this weekend. |
Pinging @zbruhnke |
so sorry all! was in Virginia all last week and SF the week before, I'll work on checking out these changes and getting them merged in as well as setting up a spec and working on some new features. I'm overwhelmed by the support for bloggy, for the longest time I thought noone was even using it so I am glad it has been useful to you all and I will do a better job of maintaining it so it can be even more useful. Pleases continue opening issues and/or feature requests and I'll dive into them in the coming days/weeks. Thanks again for your contributions everyone! -Best |
@whatasunnyday I have pushed version 0.2 and this should be live on ruby gems now so the generator should be back up and working for you! Thanks @erictheise! |
Docs read that you can do rails g jekyll:blog NAME and it will create directory public/NAME but it only returns public/blog.
The text was updated successfully, but these errors were encountered: