Hi,

If I understand well, the purpose of deploy action is only to push the content to the endpoint. If the destination supports revisions, a new unpublished revision is created. The second action, publish, take care of publishing this revision.

Would the publish action required if my destination website does not support revision? I ran multiple tests and the destination always show the last version of the content. Would it be safe to avoid this publish action to run (avoid the queue deploy_publish for example) or would I miss something?

Thanks,

Comments

vbouchet created an issue.