Version Control Summary Optional
complete
Parson, Dan
Love the new version control capabilities, I feel like it really impacts initial build time requiring change summary with every publish. Please make the summary optional. So that we can fill it out once we have a working WF
Log In
J
Jordan Pizza
complete
J
Jordan Pizza
in progress
J
Jordan Pizza
Worth noting that you can test your workflow, which will automatically create a version if you've made changes since your last publish.
These will show as "Workflow Manual Test" in the versions panel.
Parson, Dan
Jordan Pizza, under general purposes I would highly agree, but currently building a workflow with a webhook trigger, I can't test that workflow until I publish changes since its triggered by an external event. So, if the workflow is all self-contained Test will work just fine, but otherwise the changes need to be published
J
Jordan Pizza
Parson, Dan: Sounds good! We have some ideas around separating the "Publish" and "Saving" processes, and Version Control was the first step. Definitely look for this in the future.