Publish personal GitHub pages #354
Comments
Seems reasonable. Currently our deploy code is really simple. How can we detect if it is a personal repo vs a project repo? By looking at the structure of the remote? I'd be happy to do this, but I don't want it to be a config option, so how can we figure it out automatically? |
Thanks for looking into this request. As far as I understand, a GitHub user can only have one personal repo, and that repo must be named |
Publish personal GitHub pages: I would vote for such an option too. |
This would also support organization pages! |
Ok, by looking at my personal repo, I think this is how we need to do it. Look at the output of if it is |
Or, alternatively, we could just add the branch as an arguement to the gh-deploy command so you specify master. i.e. |
Agreed. The latter would provide more flexibility. |
I also think the latter is also safer. I'm a bit scared about wiping the master branch on a repo by incorrectly guessing the URL. So lets have the user provide it. :) |
I've switched over to using mkdocs for my personal page and am really liking the output.
I'd like to request that
gh-deploy
be extended to support personal GitHub pages also. Unlike project pages, personal pages must have repository names<username>.github.io
, and the project is published to themaster
branch instead ofgh-pages
. Everything works fine if I do it manually so I presume supporting personal pages automatically should not be too difficult.Edit: I have a hacky Makefile that emulates
gh-deploy
(assumes that the markdown source is on a branch calledmkdocs
and deploys tomaster
):site: git checkout mkdocs mkdocs build git checkout master cp -R site/* . rm -rf site echo Ready to commit and push
The text was updated successfully, but these errors were encountered: