build: Workflow to attach Lab as ZIP to release#7951
Draft
distantnative wants to merge 1 commit intodevelop-minorfrom
Draft
build: Workflow to attach Lab as ZIP to release#7951distantnative wants to merge 1 commit intodevelop-minorfrom
distantnative wants to merge 1 commit intodevelop-minorfrom
Conversation
distantnative
force-pushed
the
feat/labs-docs
branch
from
d0aadff to
41169d3
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Adds a new "Panel Lab docs" workflow that automatically builds and attaches the Lab docs JSONs as ZIP to each GitHub Release. That way we could finally offer instructions at https://getkirby.com/docs/reference/plugins/ui#access-the-panel-lab-locally
Lab.zipfrom release.panel/dist/ui/Testing
The workflow can also be triggered manually via
workflow_dispatch. Adry_runoption is available to run the full build and packaging pipeline without uploading anything to a release. At least something, but I haven't thought of a real good way to know/test whether this all works as imagined.