Deploy Fix #1692
Merged
Deploy Fix #1692
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
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.
This is a small PR relating to a bad way to capture path information I suggested in #1653. The path I suggested works in a staged deploy, but a real deploy has the
deployfolder as a git repo which is whatrev-parsepicks up. This corrects that oversight.This PR addresses the build failure of
masterwhich only failed due to the deploy failure and not a code failure. Subsequent commits tomasterwill pass regardless of other (passing) merges, however deploys will fail until this PR is merged.