gitlab-ci: Disable shallow clones
authorBen Gamari <ben@smart-cactus.org>
Sat, 8 Jun 2019 18:02:02 +0000 (14:02 -0400)
committerBen Gamari <ben@smart-cactus.org>
Sat, 8 Jun 2019 18:02:02 +0000 (14:02 -0400)
commitb2f106f5544e4c71bb07df4acb9d2b5ed184a7e3
treed1df8f53e99817f8d87b817f4baa81bf3dcaea51
parent709290b01c3c63137d863d6fdd97dabdfe47eb29
gitlab-ci: Disable shallow clones

Previously we were passing `--unshallow` to `git fetch` in the linting
rules to ensure that the base commit which we were linting with respect
to was available. However, this breaks due to GitLab's re-use of
working directories since `git fetch --unshallow` fails on a repository
which is not currently shallow.

Given that `git fetch --unshallow` circumvents the efficiencies provided
by shallow clones anyways, let's just disable them entirely.

There is no documented way to do disable shallow clones but on checking
the GitLab implementation it seems that setting `GIT_DEPTH=0` should do
the trick.
.gitlab-ci.yml