I have a question about configuring the webhook which kicks off the provider verification build on pact change. • _as per: https://docs.pact.io/pact_nirvana/step_6#add-can-i-deploy-webhook-to-pact-broker_ It says: _"and use webhook templates to pass the URL of the changed pact to the build along with the provider branch and provider sha (git commit)."_ Passing the pact url makes perfect sense..., but what is the purpose of passing along the provider branch and commit to the verification build? Isn't the point to run the verification build on master anyway, so the branch and commit would be fetched within the build itself?

you want tp verify the pact against the head of providers main branch plus deployed and released versions. you do that by checking out the version of code deployed or released to any env

Ah okay. I guess it depends on the setup then. For us, code only reaches master once it's in production. But I understand that for many other people, there are separate release branches etc. Makes sense, ty!