You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could you consider adding additional logging for the git command when running on makefile / build?
Two scenairos:
-- add -v to git for just a tad but more info (regardless of DEBUG=0)
--When DEBUG=0 set GIT_TRACE=0 -> nothing changes
--When DEBUG=1 set GIT_TRACE=1 -> with this GIT_TRACE will provide deeper tracing for tracking
Put GIT_TRACE=x in with git command
The -v (verbose) and trace options in Git provide different levels of detailed output and are used for different purposes. Here’s a breakdown of the differences between them:
-v (Verbose)
Purpose: Provides additional details and feedback about the command being executed.
Use Case: Useful for getting more information about what's happening during a Git operation, such as cloning, pushing, pulling, or committing.
Level of Detail: trace provides much more detailed and low-level information compared to -v.
Intended Audience: -v is useful for general users who need a bit more context, while trace is more suitable for developers or advanced users who need to debug and understand Git's internal processes.
Both options can be extremely helpful, but the trace option gives a more in-depth look under the hood, which can be invaluable for diagnosing tough issues.
Thank you again!
The text was updated successfully, but these errors were encountered:
Could you consider adding additional logging for the git command when running on makefile / build?
Two scenairos:
-- add -v to git for just a tad but more info (regardless of DEBUG=0)
--When DEBUG=0 set GIT_TRACE=0 -> nothing changes
--When DEBUG=1 set GIT_TRACE=1 -> with this GIT_TRACE will provide deeper tracing for tracking
Put GIT_TRACE=x in with git command
The
-v
(verbose) andtrace
options in Git provide different levels of detailed output and are used for different purposes. Here’s a breakdown of the differences between them:-v
(Verbose)trace
GIT_TRACE
,GIT_TRACE_PACKET
,GIT_TRACE_PERFORMANCE
, etc.Key Differences
trace
provides much more detailed and low-level information compared to-v
.-v
is useful for general users who need a bit more context, whiletrace
is more suitable for developers or advanced users who need to debug and understand Git's internal processes.Both options can be extremely helpful, but the
trace
option gives a more in-depth look under the hood, which can be invaluable for diagnosing tough issues.Thank you again!
The text was updated successfully, but these errors were encountered: