Pelican has built-in support for GitHub Pages. However, I noticed that the ghp-import command might screw up the commit log if your GitHub Pages and your Pelican source code share the same branch name.

According to the document of GitHub Pages, the user pages should be committed to master branch (instead of gh_pages.) If you have answered master while pelican-quickstart was asking for the GitHub Page branch, then ghp-import will automatically commit the generated output to the master branch. Consequently, the git repository will be screwed up.

My solution is to create a pelican-source branch for Pelican source code, and commit the generated output to the master branch. This will fix this issue without any problems.