This repository was archived by the owner on Mar 18, 2018. It is now read-only.
Publishing with a relative symlink #45
Merged
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
Member
|
@Jaconil I see, but tests are not passing, and we don't need to expose relativeReleasePath |
Jaconil
force-pushed
the
relativeSymlink
branch
from
11f365d to
ba32a45
Compare
Contributor
Author
|
@neoziro I made some changes following your comment ;) |
Member
|
@Jaconil good thanks |
gregberge
added a commit
that referenced
this pull request
Jan 19, 2015
Publishing with a relative symlink
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
Changes the publishing symlink to be relative instead of absolute. This update fixes publishing which doesn't work when the deployTo option is a relative path.
Relative links are better if the directories they target are moved or mounted elsewhere for example.