Upgrading from 1.17.0 to 1.17.1 fails git fetch about versionize

[cabauman]

GitLab doesn't seem to be related since you said it works with the previous version, but I'll ask anyways: so, you use GitLab configuration like specified here?

GIT_STRATEGY: fetch
GIT_FETCH_EXTRA_FLAGS: --unshallow
GIT_DEPTH: 0

There's only a one commit (one file) difference between the two versions which is related to working directory. Does anything stand out? I'll see if I can reproduce the issue with GitHub when I get some time.

[swarooprooney]

was this resolved? I am facing the same issue with azure devops pipeline with github actions

[mumby0168]

This was mentioned in #42

Setting the git fetch depth to 0 has just worked for my pipeline in ado:

stages:
- stage: conventionalcommit
  displayName: conventional commit
  jobs:
  - job: conventionalcommit
    pool:
      vmImage: "ubuntu-latest"
    steps:
      - checkout: self
        fetchDepth: 0
        persistCredentials: "true"

cc @swarooprooney

[jsyrjala]

For me this in worked in GitLab

variables:
    GIT_STRATEGY: fetch
    GIT_DEPTH: 1000

Having this parameter there caused some error about depth and unshallow not being compatible.

GIT_FETCH_EXTRA_FLAGS: --unshallow

GitLab has default git depth of 20 or 50:
https://microfluidics.utoronto.ca/gitlab/help/ci/pipelines/settings.md#limit-the-number-of-changes-fetched-during-clone