git push force

So now from #129 I have function that restore git repo from HEAD~1 but when I have pushed the commit I to update remote I need to use git push -f.

if this is how push works every time then I need to a way to check if push will overwrite commits so I would be able to reject it when user don’t use force.

[wmhilton]

🎉 This issue has been resolved in version 0.24.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[wmhilton]

A deep search of the git source code reveals that git push -f is a client side implementation detail. So yes, we must check that what we are pushing follows the 4 rules laid out in the comment ourselves before doing a push:

		/*
		 * If the update isn't already rejected then check
		 * the usual "must fast-forward" rules.
		 *
		 * Decide whether an individual refspec A:B can be
		 * pushed.  The push will succeed if any of the
		 * following are true:
		 *
		 * (1) the remote reference B does not exist
		 *
		 * (2) the remote reference B is being removed (i.e.,
		 *     pushing :B where no source is specified)
		 *
		 * (3) the destination is not under refs/tags/, and
		 *     if the old and new value is a commit, the new
		 *     is a descendant of the old.
		 *
		 * (4) it is forced using the +A:B notation, or by
		 *     passing the --force argument
		 */

which, written another way, I think ends up being:

Require --force for a push if:

• the ref is a tag that already exists on the server
• the ref is a branch that already exists on the server and the new oid is NOT a descendent of the old