summaryrefslogtreecommitdiff
path: root/compiler/codeGen
diff options
context:
space:
mode:
authorBen Gamari <ben@smart-cactus.org>2019-06-08 14:02:02 -0400
committerBen Gamari <ben@smart-cactus.org>2019-06-08 14:02:02 -0400
commitb2f106f5544e4c71bb07df4acb9d2b5ed184a7e3 (patch)
treed1df8f53e99817f8d87b817f4baa81bf3dcaea51 /compiler/codeGen
parent709290b01c3c63137d863d6fdd97dabdfe47eb29 (diff)
downloadhaskell-b2f106f5544e4c71bb07df4acb9d2b5ed184a7e3.tar.gz
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.
Diffstat (limited to 'compiler/codeGen')
0 files changed, 0 insertions, 0 deletions