Skip to content

Force push even if remote ref is an unknown commit

This fixes #3 (closed): if remote Git ref is unknown in the git-mapfile of the Mercurial repo and force is True, we push it anyway.

This is consistent with the idea of force-pushing. In the case of Heptapod, this condition is unexpected, the remote being just a mirror of the Mercurial repo, hence the warning.

Note also that Heptapod is always force-pushing to the Git repo that GitLab reads and listens to.

Merge request reports