I've just created a GitHub Pages for my repo. It's a nice idea, but I don't like the way I have to create a separate branch for my web pages. In effect, github makes us squash two repos in one - one for the code, and another the html.
This is a bad idea. Conceptually, the gh-pages branch isn't "really" a branch off an existing one, but a completely distinct branch. I argue that that's not the way git is supposed to work. It creates a complication: there's no way for the branches to "talk" to each other. It means that I can't generate html from my main branch (maybe I want to run a doc generator on my python code, maybe I have markdown text from which I want to generate both man pages, info and html). A better approach would be for the user to have to create a configuration file, maybe called gh-pages, in the root of the repo. The most important thing it will do is point to a directory in my repo that contains my pages. That way, I don't have to keep switching branches - one for code, one for html. Github looks at my repo, determines that there is a gh-pages file, reads it, and serves pages accordingly. -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to git...@googlegroups.com. To unsubscribe from this group, send email to github+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/github?hl=en.
