Right now when deploying an artifact to a branch, current functionality is to pull in and checkout what is already included in the destination branch specified, build artifact, and then commit and push back to the same branch. When used in a multidev context, this makes it such that you cannot use Pantheon's native multidev -> dev merge functionality. However, if we started all branch deployments by pulling in master from Pantheon instead, this functionality could be maintained. I think this would be a common-sense enhancement to this extension. Modifications of Polymer core might be necessary.
Right now when deploying an artifact to a branch, current functionality is to pull in and checkout what is already included in the destination branch specified, build artifact, and then commit and push back to the same branch. When used in a multidev context, this makes it such that you cannot use Pantheon's native multidev -> dev merge functionality. However, if we started all branch deployments by pulling in
masterfrom Pantheon instead, this functionality could be maintained. I think this would be a common-sense enhancement to this extension. Modifications of Polymer core might be necessary.