This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
Add failongiterror as parameter to report any git error as NuKeeper e… #1140
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.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
A new option is added. When the option FailOnGitError is set the run failes when the call to get the available versions failes.
This is only the first part of a fix for #930
On most of git calls the error is ignored and NuKeeper notifies success.
🆕 What is the new behavior (if this is a feature change)?
A new option
--failongiterror
is introduced and when this option is set an error in a git call results in an error of NuKeeper.In the current process the option is only used when searching for the available package versions.
💥 Does this PR introduce a breaking change?
No, the default behaviour is unchanged.
🐛 Recommendations for testing
📝 Links to relevant issues/docs
🤔 Checklist before submitting