Skip to content

git describe in an override-build is always claiming to be dirty #942

@lengau

Description

@lengau

Bug Description

This is upstreamed from canonical/snapcraft#5831

If you have a spread/.extension file, git describe --dirty in an override-build will always show the repo as dirty because spread.yaml and spread/.extension don't get copied into the build directory.

This is causing Charmcraft 4.0.0 to appear to be dirty.

To Reproduce

Check out the 4.0.0 tag of Charmcraft and pack it

Environment

My machine, launchpad, etc...

snapcraft.yaml

...

Relevant log output

n/a

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions