-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contribution workflow: How to include additional files (e.g. plugin zip) in a PR? #6
Comments
This could be confusing, relative URLs are usually tied to the site context. What if blueprints accepted bas64 encoded data? This would remove the need for putting the data on a server. |
The Playground could help some URLs by rewriting dynamically couldn't it? That is, recognize that it's a Github link, and if it's not the right |
Related: #18 |
To resolve this issue, we'll need to document the expected URL for all assets is the https://raw.githubusercontent.com/ URL pointing to the proposed branch. |
Documented in d2f9f8d |
Contributing Guidelines say:
However, it's unclear how to actually reference these files in blueprint.json in a PR. That blueprint can ship URLs pointing to the newly proposed branch, but once that branch is merged these URLs will need to magically start pointing to
trunk
.Two solutions that came to mind:
{ "step": "installPlugin", "pluginZipFile": "./plugin.zip" }
. This would be a breaking change because relative URLs are now relative to the client site URL. Maybe that's fine, though? Or perhaps we could ship a new resource type, like "blueprint-relative-url"?cc @bgrgicak @brandonpayton @dmsnell for ideas
The text was updated successfully, but these errors were encountered: