Bugfix: Pass zero ref to --internal-updated-from on clone

[gabyx]

Thanks for merging.

We should pass a null ref to --internal-updated-from such that we know we have newly cloned the release clone. Might come handy in the future.

Furthermore related to this problem and a bit trickier:

• I installed with a local path as the clone url -> /data/git/repositories/githooks.git (on a gitea server)
• This results in a stupid legacy_transform_after_update because --depth 1 is not honoured for local paths (git stuff) and the if [ "$COMMIT_COUNT" != "1" ] passes... :bomb: This fix resolves this problem!

[coveralls]

Pull Request Test Coverage Report for Build 833

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.07%) to 80.632%

---

Files with Coverage Reduction	New Missed Lines	%
install.sh	1	68.48%
<!--	Total:	1		-->

Totals
Change from base Build 830:	0.07%
Covered Lines:	2373
Relevant Lines:	2943

---

💛 - Coveralls