man-group / man-group/notebooker

Be more verbose when we are inspecting git for SHA differences

Open
#156 0 comments 0 reactions 1 assignee View on GitHub

@ceallen is already working on this.

Since Oct 11, 2023.

Dominant language
Python
Stars
939
Forks
95
Avg merge
9d 1h
Merged PRs (30d)
1

Description

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).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.