-
Notifications
You must be signed in to change notification settings - Fork 175
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
How to upgrade? #11
Comments
I believe this best way to upgrade is
That's it! I might be missing something so please do try it and let us know! |
Thanks, Hamel! :) |
@wshuyi actually I don’t think you have to even rename your old repo, I believe when you click the “use template” button you get the option to name the repo |
Word processor
"@wshuyi actually I don’t think you have to even rename your old repo, I believe when you click the “use template” button you get the option to name the repo" Github can't clone the repo as it already exists if you try to (re)apply the template to an existing repo |
Ugh! There doesn't appear to be a nice clean way of doing this If you rename the old repo you have to remember to delete the custom domain before your new website can forward to it And BTW the posts in the _posts directory are not updated due to the previously noted timestamp issue |
Hi Jeremy,
Thank you so much for this project. It made blogging really easy.
I have already set up a blog yesterday and just found a new feature you posted on twitter (the auto conversion of word docs). I would like to have a try. Do I need to repeat the whole procedure to reset a new blog? Or can I get the template upgraded directly with a command?
Looking forward to your reply. Thanks!
The text was updated successfully, but these errors were encountered: