Hi There! I have a question regarding the documentation for the CI/CD setup guide, specifically step 7, Diamond level. In the chart in the section "Let's record our deployments," for the provider workflow in the PR validation pipeline part, we first: 1. verify pacts with [mainBranch] and [deployedOrReleased] selectors, which checks if my provider PR is compatible with mainBranch consumers in all environments. Why is it necessary to then use

can-i-deploy --to-environment ...

when the result is already known from the previous step? Could someone help me understand this part? Everything made sense up until now. Thanks!

It’s a fair question. It’s usually because there can be other steps in that pipeline that might introduce changes that invalidate that - so it’s probably more out of an abundance of caution. Also, I think it’s simpler to always use

can-i-deploy

before attempting a deployment as a matter of consistency

Thanks for providing more details on this 👍 Since we don't have such a situation, it's a bit challenging to understand it properly.