[scripts] Added basic safety to the repository installation Bash script#25017
Open
serious-angel wants to merge 1 commit into
Open
[scripts] Added basic safety to the repository installation Bash script#25017serious-angel wants to merge 1 commit into
serious-angel wants to merge 1 commit into
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Dear Developers and Artists,
Thank you for the marvel, art you do!
Description
The main issue is that it's not the first time the publicly proposed script does not complete successfully somewhere in the middle, and since no checks happen, the commands just get executed regardless. A person may not even notice some command failed above if the output from the next commands fills up the screen, too.
I am not sure the initial reason the script had no execution checks, but just in case, what do you think about the command group, due to the here-doc?
Or would it look better with the previous command core check?:
Check the exit status code of the previous command
There's a less recommended alternative:
Set the bash-opt to stop execution on any command fail
May I ask, why don't you use
;to separate the commands?Reviews