refactor: update workflow with new pcl command#191
Merged
Conversation
e08d2df to
38e2efe
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
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.
Ref ENG-2236
Updates PCL documentation to reflect the new declarative
pcl applyworkflow, replacing the old imperativepcl store+pcl submitflow.pcl applyis now the primary deployment command: CLI reference, quickstart tutorial, and a new dedicated guide (apply-assertions.mdx) all walkusers through the
credible.toml+pcl applyflowpcl storeandpcl submitfully removed from docs: All references, examples, and the oldstore-submit-assertions.mdxpage are gonepcl applycreates a release; you then review and deploy in the platform to activate assertionspcl buildno longer a separate step: Removed from workflows sincepcl applybuilds automaticallypcl applyhandles itCLI → Platform → DAinstead ofCLI → DA+CLI → Dapp