use generic wording in 30_check_backup_and_output_url (issue925) #927
Conversation
This file contains hidden or 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
Member
Author
|
I tested it and it works for me. |
jsmeix
deleted the
use_generic_wording_in_check_backup_and_output_url_issue925
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use generic wording in error messages
because prep/default/02_translate_url.sh
may translate a BACKUP_URL into an OUTPUT_URL
so that errors in a BACKUP_URL may appear when
testing the translated/derived OUTPUT_URL
see #925
First steps to be prepared for 'se -e' which means
replacing COMMAND ; StopIfError ...
with COMMAND || Error ...