Skip to content

Be more verbose when we are inspecting git for SHA differences #156

@jonbannister

Description

@jonbannister

If the SHA has not changed, there is no logging.INFO message to inform users that we have actually checked git. This means that git pulling can be activated without the user really knowing (until it eventually pulls when the SHA of origin changes vs. HEAD).

Metadata

Metadata

Assignees

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