Use mkdir(1) just once. #1264
Merged
Use mkdir(1) just once. #1264
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
The mkdir(1) utility support multiple arguments, so it's possible to use it once to create more than one directory.
|
Deploy request for nginx-kubernetes-ingress rejected. Rejected with commit 7f143d7 https://docs.netlify.com/configure-builds/environment-variables/#sensitive-variable-policy |
Dean-Coakley
reviewed
Dec 8, 2020
Contributor
Dean-Coakley
left a comment
Dean-Coakley
left a comment
There was a problem hiding this comment.
This change looks good.
However, with this change these files will have mixed indentation. Can you change back to tabs?
Dean-Coakley
approved these changes
Dec 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The mkdir(1) utility support multiple arguments, so it's possible
to use it once to create more than one directory.
Proposed changes
Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue here in this description (not in the title of the PR).
Checklist
Before creating a PR, run through this checklist and mark each as complete.