MicrosoftThis is a great extension, but we are having challenge with the CI portion of this approach. When we manually publish from the collaboration branch, this does two things. Pushes changes to live move AND generates templates into the publish branch of GIT. In normal CI/CD where no cherry picking is needed, all code originates from a branch pull request into the collaboration branch.
Using the Validate and Deploy option purposely does not push the templates to the publish branch by design to support cherry picking. But having said that, automating the full behavior of the "Publish" action under non cherry-picking scenarios (which, for us, is more common) is required in order to be able to deploy the changes that are now in LIVE mode but NOT in the publish branch where the CD pipeline (using the Deploy) option would promote to QA.
It would appear that, if we wanted to fully automate the manual publish that occurs on the collaboration branch, we would have to add a couple more tasks to the release: 1: Use the Validate method to generate the templates as an artifact and then 2: Add a step in the release pipeline to perform the push of these templates into the publish branch. Does this sound correct or am I missing something?
