Closes #71: Apply logging consistently for all branch operations #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arthanson
approved these changes
Sep 5, 2024
| # Update Branch status | ||
| logger.debug(f"Setting branch status to {BranchStatusChoices.SYNCING}") |
There was a problem hiding this comment.
would be good to include branch name in all debug log messages
There was a problem hiding this comment.
We include the branch name in the initial INFO message at the start of each operation, which seems like it should be sufficient IMO. I'm wary of making the logs too verbose, but it's something we can re-evaluate over time for sure.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #71
print()statements from early development