Affected Packages
Problem
In some git solutions like Bitbucket, git fetch --deepen [Number] does not work.
When the command changeset version is runned in a step from bitbucket-pipeline, that is using a shallow clone, the step locks.
This happens because the changeset version try to get more commits from history using the git fetch --deepen command
Proposed solution
Throw an error if the returning code from git fetch --deepen [Number] is different from 0.
https://github.com/atlassian/changesets/blob/main/packages/git/src/index.ts#L165
Affected Packages
Problem
In some git solutions like Bitbucket,
git fetch --deepen [Number]does not work.When the command
changeset versionis runned in a step frombitbucket-pipeline, that is using a shallow clone, the step locks.This happens because the
changeset versiontry to get more commits from history using thegit fetch --deepencommandProposed solution
Throw an error if the returning code from
git fetch --deepen [Number]is different from 0.https://github.com/atlassian/changesets/blob/main/packages/git/src/index.ts#L165