Skip to content

Add error messages on shallow clones #5

@nbrns

Description

@nbrns

When using the tool on a shallow clone of a repository, the resulting version can to be 0.0.0.
I faced the problem when using GitLab runners, which use shallow clones by default.

The solution for me was to ensure to have an unshallow clone by adding git fetch --unshallow to my CI.
If you ask me, a hint to make sure to use an unshallow clone in case of a 0.0.0 return would be nice.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions