-
Notifications
You must be signed in to change notification settings - Fork 652
Add a debug option to the command line #2104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions. |
This is perhaps something we should consider for #2275. |
Agree |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. |
This issue was closed because it has been stalled for 30 days with no activity. Thank you for your contributions |
There are multiple ways of running GitVersion (command line, devops tool etc), and the behaviour can be non-obvious, it makes sense to optionally report this as part of the command line.
This makes it easier to debug issues such as #2094 where unexpectantly the config file has to be explicitly specified.
The text was updated successfully, but these errors were encountered: