Skip to content

Conversation

@jandubois
Copy link
Member

It is redundant because it is already the default.

I suspect that we used it because in many places we needed to specify fetch-depth: 0 to get all the tags. But with one exception for the colima test, this is no longer the case, so I think we should get rid of all of these.

See also: #3820 (comment)

It is redundant because it is already the default.

I suspect that we used it because in many places we needed to specify
`fetch-depth: 0` to get all the tags. But with one exception for the
colima test, this is no longer the case, so I think we should get rid
of all of these.

Signed-off-by: Jan Dubois <[email protected]>
@jandubois jandubois added this to the v2.0.0 milestone Aug 16, 2025
Copy link
Member

@afbjorklund afbjorklund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually it is just an optimization for huge repos, but I don't think it (shallow clone) is needed here.

@jandubois
Copy link
Member Author

Usually it is just an optimization for huge repos, but I don't think it (shallow clone) is needed here.

Shallow clone is already the default. This is a no-op change, just removing the explicit setting of the default value.

    # Number of commits to fetch. 0 indicates all history for all branches and tags.
    # Default: 1
    fetch-depth: ''

@jandubois jandubois merged commit 5efb04b into lima-vm:master Aug 16, 2025
62 of 63 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants