Hello 👋 Sorry if this has already been asked. I've just got a question around verifying contracts by provider that were published by branches on the consumer so get tagged with the branch name. We have found that we're having to update our provider verification code (consumerVersionTags) each time to reference the branch where the contract that was published from. I've read this page in the pact documentation and it suggests using the using the git branch name in ConsumerVersionSelectors and ensure the git branch for both the provider and the consumer are the same when the contract gets published and verified. We have tried this and it appears to work but means we'd need to remember to do this every time going forward. This document also mentions dynamically determining the tags of the feature branch which sounds like a much better option. Has anyone done this and got some examples or other suggestions?

The CI/CD workshop (howtolearn) shows how to address this

Here are a number of useful hands-on labs that teach all of the key concepts: https://docs.pactflow.io/docs/workshops and https://docs.pact.io/implementation_guides/workshops

☝️

Thanks for the links Matt but is there anything more specific that covers verifying contracts on branches?

are you using “tags” or “branches” and “releases”?

We have been using tags but have recently read about branches, we're already using the webhook to trigger the verification but unless we change the consumer tag on the provider to point to the branch it never verifies the contract published from branch