Replace non-ASCII character in comment #3050
Merged
Conversation
This file contains 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 curly apostrophe in the comment is causing AWS EB CLI to fail. https://stackoverflow.com/a/55988700/594211
|
@jrc thanks! Definitely not needed if that's the sort of problem it's introducing... |
Ortega-Dan
pushed a commit
to Ortega-Dan/gitignore
that referenced
this pull request
Jun 26, 2019
The curly apostrophe in the comment is causing AWS EB CLI to fail. https://stackoverflow.com/a/55988700/594211
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.
Reasons for making this change:
The curly apostrophe in the pipenv comment (added in commit 7079791) is causing AWS EB CLI to fail. https://stackoverflow.com/a/55988700/594211