Skip to content

do not send git log stdout to debug logs anymore. too much noise.#155

Merged
levibostian merged 1 commit intomainfrom
git-logs-debug-stop
Mar 15, 2026
Merged

do not send git log stdout to debug logs anymore. too much noise.#155
levibostian merged 1 commit intomainfrom
git-logs-debug-stop

Conversation

@levibostian
Copy link
Copy Markdown
Owner

Related GitHub Issues

Problem

git log output is just wayyyyy too noisey. It has made debugging difficult to do. Sure, there can be an error in the git log command. if there is, I think we can make something like a script that you install that runs for the 'get latest release' step that logs all parsed commits and that will help debug git commits that were incorrectly parsed.

Solution

Because this is a one-off case for the logger and we dont want to modify any other command behavior, add an optional parameter to exec.run that changes this behavior. So the default behavior doesn't change.

Testing

  • Added automated tests.
  • Manually tested. If you check this box, provide instructions for others to test, too.

Going to turn on debug mode for this PR and see if it works as expected.

Notes for reviewers

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 15, 2026

decaf

Running deployments in test mode. Results will appear below.
If this pull request and all of it's parent pull requests are merged using the...

...🟩 squash 🟩 merge method... 🌴 It will not trigger a deployment. No new version will be deployed.

Learn more
Latest release: 0.12.0
Commit of latest release: 7a66814

Commits since last release:
- do not send git log stdout to debug logs anymore. too much noise.

Related GitHub Issues

<!-- Link to any related GitHub issues that this pull request addresses or closes. -->

Problem

<!-- A clear description of the problem that this pull request is solving. -->

git log output is just wayyyyy too noisey. It has made debugging difficult to do. Sure, there can be an error in the git log command. if there is, I think we can make something like a script that you install that runs for the 'get latest release' step that logs all parsed commits and that will help debug git commits that were incorrectly parsed.

Solution

<!-- Describe the approach you took to solve the problem and the changes made in this pull request. -->

Because this is a one-off case for the logger and we dont want to modify any other command behavior, add an optional parameter to exec.run that changes this behavior. So the default behavior doesn't change.

Testing

<!-- Choose one of the below options for how you tested the code change. Include any specific setup or instructions for testing. -->

  • Added automated tests.
  • Manually tested. If you check this box, provide instructions for others to test, too.

Going to turn on debug mode for this PR and see if it works as expected.

Notes for reviewers

<!-- If there is any additional information you would like to share with the person reviewing this pull request, please provide it here. -->

...🟩 rebase 🟩 merge method... 🌴 It will not trigger a deployment. No new version will be deployed.

Learn more
Latest release: 0.12.0
Commit of latest release: 7a66814

Commits since last release:
- do not send git log stdout to debug logs anymore. too much noise.

@levibostian
Copy link
Copy Markdown
Owner Author

Checked the circle logs, which have debug enabled at all times, and the output looked good. All commands seem to still send stdout/stderr to console except for git log.

@levibostian levibostian merged commit ed4f0cb into main Mar 15, 2026
11 checks passed
@levibostian levibostian deleted the git-logs-debug-stop branch March 15, 2026 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant