Support Superblocks resources not directly at repo root #19
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
ahmetkucuk
approved these changes
Mar 6, 2024
taha-au
force-pushed
the
ts/support-sb-path
branch
from
c1e07ff
to
ad409ed
Compare
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 PR changes the meaning of the
pathinput to be the Superblocks root path relative to repo root.In the entrypoint script, we remove env var support of
SUPERBLOCKS_CONFIG_PATHand instead start taking in aSUPERBLOCKS_PATHenv var.With these changes, we truly support Superblocks assets living in a nested directory within a repo.
Sibling of superblocksteam/import-action#28