Allow for any number of whitespace characters between the COPY/ADD commands for file syncing #629
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
…ocal and remote files when parsing for file syncing
|
Wow, thanks! Less code and more robust. 👍 |
|
Merging in #668 |
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.
Was banging my head for a little bit why the file syncing wasn't working, and realized that the Dockerfile had an extra space between the local and remote files specified in the COPY command (e.g. COPY ./app /app #Notice two spaces between them). Technically it's a valid Dockerfile, and thought this may help someone else who runs into a similar issue for some reason.
Release Playbook