Add --no-history option to not push parent history for gh_deploy

[wlmchen]

No description provided.

[oprypin]

Thanks for the contribution. This will be accepted.

[oprypin]

Actually you know what? I have tried all kinds of combinations and I still can't guess what this flag does, or, to me it appears to not do anything. I used mkdocs gh-deploy -b test --no-history and it still creates a new commit on top of old ones.

[oprypin]

Is it supposed to affect the time of creation of a new branch, or is it about an existing destination branch?

[wlmchen]

It affects the destination branch. If the destination branch already contains commits from a previous deployment, using mkdocs gh-deploy will push a commit on top of the previous commits. Using --no-history sets the newest deployment as the initial and only commit for the destination branch.

An example scenario is simply running mkdocs gh-deploy -b test without --no-history multiple times, which will create duplicate commits (In reality these will be deployments for different commits). Using --no-history will result in only one commit.

[pawamoy]

So it seems this PR simply makes use of ghp-import's no_history option, which in turn creates a commit without a parent one. I'll have to test it on one of my projects to really see how it behaves.

[oprypin]

Sorry for the delay.

Indeed it works as per the description.

Replace the whole Git history with one new commit.