Improve debug output. #512
Closed
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
cwarlich
force-pushed
the
feature/git_logging
branch
4 times, most recently
from
ea843e2 to
b0e964a
Compare
cwarlich
force-pushed
the
feature/git_logging
branch
from
b0e964a to
22f20a1
Compare
|
Sorry for the forced pushes: The test is fine now. |
rasa
approved these changes
Jan 3, 2025
|
Thanks for working on improving yadm! There is built-in support in git itself for printing commands that are executed. You get it by setting Please rebase this on develop instead of master. Also, |
|
Am 05.01.25 um 17:25 schrieb Erik Flodin:
There is built-in support in git itself for printing commands that are
executed. You get it by setting |GIT_TRACE=1| when running e.g. yadm.
Thanks, I just didn't knew.
So I wonder if it's worth having similar support also in yadm. What do
you think?
You are absolutely right, this doesn't make much sense.
|
|
Closing this then based on the last comment. |
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.
Currently, when setting the DEBUG environment variable, yadm prints some additional info w.r.t. what it is doing. This is only of marginal help particularly for anyone new to yadm development: Whenever debuging the yadm script, one really wants to know exactly what git is doing "under the hood" when running yadm commands.
This patch does just that: When DEBUG is set, it additionally prints all instances where the yadm script runs git. It does that in green allowing to distinghuish from the hand-written debug messages.